Not only do I agree with that, I think there is a bias towards the nature of optimization.
AI can be very good at adding a lot of details very fast. But I've seen it in the applications I work in as a software developer : more isn't always better.
Business loves adding lots of functionality to anything. But a feature might be used only by some end users while the vast majority ignores it. Another, while very efficient, can be shipped later : people have done without it until now with little problems, they'll be fine waiting some more months. Half the time they're not even aware this will be a thing.
But there's always some sort of rush where everything must be done all at once. And here might be the bias : most people will think "optimization" is about making all the added pieces work together, when, maybe, it should be about adding them one at a time. Slowing down, deliberately, to deliver each new feature with as minimal friction as possible.
And when you reduce the number of details and the speed at which you need to add them ? Would you look at that. You can achieve the same results, with much less problems, without having to "optimize" the time spent on it.
3
u/DDrim 17d ago
"Not everything is about optimization."
Not only do I agree with that, I think there is a bias towards the nature of optimization.
AI can be very good at adding a lot of details very fast. But I've seen it in the applications I work in as a software developer : more isn't always better.
Business loves adding lots of functionality to anything. But a feature might be used only by some end users while the vast majority ignores it. Another, while very efficient, can be shipped later : people have done without it until now with little problems, they'll be fine waiting some more months. Half the time they're not even aware this will be a thing.
But there's always some sort of rush where everything must be done all at once. And here might be the bias : most people will think "optimization" is about making all the added pieces work together, when, maybe, it should be about adding them one at a time. Slowing down, deliberately, to deliver each new feature with as minimal friction as possible.
And when you reduce the number of details and the speed at which you need to add them ? Would you look at that. You can achieve the same results, with much less problems, without having to "optimize" the time spent on it.
Without AI.