Hacker News new | past | comments | ask | show | jobs | submit
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.
Ive tossed out multiple weeks of someones work, 100k LOC because they let the spaghetti monster take charge. Theres no recovery once it takes hold either, it has to be tossed. But people get comfortable not reviewing the code and it piles up. The llm is trained to reward hack its way to running/compiling code, and people assume that means it does what you want it to and move on.

I think this is largely why we're seeing so many system failures across companies, people are offshoring all the hard parts of their jobs to chat bots they assume are perfectly capable just because the code runs.

loading story #50546409
They are good at it when they are explicitly asked. The challenge is that this exercise is recursive at every level of the implementation and often the big picture needs to change based on findings during implementation. Once the AI has committed to a agreed solution, it tends to force it through at all cost and will do truly horrible things to the codebase to make it "work as designed". This is especially true when the AI spins out a subagent to do the work. The subagent has explicit instructions and will almost never push back if it hits a blocker. Instead it will force a solution to the detriment to the codebase.