@compez.eth
A few days ago, I randomly came across Amdahl’s Law, which basically says that speeding up one part of a process doesn’t necessarily mean speeding up the entire project.
At first, I thought, how is that possible?! Isn’t AI supposed to make software development faster?
But the more I thought about it, the more it made sense!
Take any product we’ve been working on for a long time, for example. Yes, I use AI to help with development, and it definitely makes certain parts of the process faster. But does that necessarily mean I can release a reliable, production-ready product sooner? Not really!
The reality is that writing code is just one part of software engineering. You still need to design the architecture, make technical decisions, integrate components, write tests, fix bugs, review security and stability, and ultimately make sure what you're releasing is actually ready for real users.
AI can speed up some of these steps too, but it won't magically eliminate the inherent complexity of engineering a real product.
Of course, if your only goal is to build something and throw it out there as quickly as possible, sure, you can do that! But just because something was built and shipped quickly doesn't mean it's a properly engineered product. Sometimes it's just garbage produced faster! :)
I think this is one of the biggest misconceptions about AI:
We've confused the speed of writing code with the speed of delivering a product.
AI is an incredible tool, but the responsibility for engineering, quality, and getting a product ready for release hasn't gone anywhere.
Writing code faster doesn't necessarily mean building software faster.