The problem was never speed

Software developers are more productive than ever before. Well, maybe more busy than ever before. Productive implies there's value returned on the backend, and while that's debatable, something that's not debatable is that developer happiness is at an all-time inflection point of uncertainty. In our new robotic age of AI, this is a trend we see in our own agency all the time, and from other content creators, agencies, and developers we connect with. What's fascinating is that the problem isn't different than what it used to be. There were always managers, executives, and product people pushing developers to build faster with less. Now we can build faster than ever with less than ever. But the problem has never been that. The problem has always been building the right thing, choosing the right direction, and having the right user experience. What's the point of building 50,000 applications and features if nobody uses them and nobody likes them? At that point you're just doing busy work. This is what's happening in so many companies. The demand to build more and more so often outweighs the understanding of whether what's being built is actually worth time and value. It's never been quantity over quality. Quantity doesn't win in a market of competition. Quality does. We all know that. Yet the intoxication of being able to build anything, anytime, from the ground up in such a short amount of time is leading people to be completely railroaded and tunnel-visioned into this idea that because I can do something, it means I should do something. These are not the same. The best developers know this. The best developers have an understanding of business, product development, marketing, and user experience. They understand how it all comes together. The best developers understand that their value is not lines of code.