Hacker News new | past | comments | ask | show | jobs | submit
Writing the code was never the hard problem, of course it required stuff like reading docs and literal typing it on the keyboard. But designing a robust system that is open for change and has the right abstractions and boundaries is what a software engineer should be mainly concerned about and AI still pretty much sucks at this. Agents can now bloat a codebase 100 times faster and they don't feel any pain while doing it.
I think they're pretty good at it. A lot of the skill of being a good developer is using gut feeling. Gut feeling here really is just a word for "the pain you feel before it happens because you made this mistake before".

We HAVE to use our gut feeling when choosing a design, because we can't make 10 designs and keep the best one. Because the tapping at keys and reading docs and setting up CI etc took so long, we usually afforded to write everything once, so it better be the right choice of design.

With AI this problem just goes away. I can ask an AI for design choices and it is rather good at listing various designs. Then I can ask it "Implement all of them, and tell me where it hurts". An hour later, I have 5 competing designs, all of which would have been a week's worth of work. None is perfect, but all are better than human written proof-of-concept code. Now I can ask the AI to review these against each other and figure out which one is easy to change, brittle, performant. Not only do I not have to have a sense for this, I can actually measure. Again, as humans we needed a sense for these performance bottlenecks, or resistance to change. But with AI, I can measure much more. Even the "bloat" problem I think is pretty easily addressable. As humans, once we spent 150% of our time budget on ONE design choice and it has 10.000 LoC, we rarely spend more time cutting that down and simplifying it. If it works, it works. With an AI, I can spend money saying "It's now 10.000 LoC, aggressively simplify and clean it up.". As humans, again we needed to use our senses to not bloat it to begin with. Because we'd not have time to un-bloat it. Remove that time restriction, and that problem also goes away.

I am not talking about UI designs, sure the AI can provide prototypes. The hard problems are how to structure the domain and backend code so that it does not become a hot mess. And AI is not good at that and benchmarks (like SlopCodeBench) and personal accounts also show that. If you let an agent fleet work on a non-trivial application the architecture will deteriorate very fast unless there is deliberate and continious steering of the architecture.
loading story #50544737
loading story #50546853