I think this is a different point, though. OP is saying, we haven't really made progress on the problem of figuring out what to build (and just as importantly - what not to build) and how to convey that effectively and set up the right feedback loops to get AI to actually deliver on that. Whereas you're saying, "Yes, I agree, the code that the agent writes has flaws in readability and design". If we can get the first part actually solved (and I'm not sure what an answer looks like - other than what we have today, which is that The Market ultimately dictates whether you've built the right thing, built enough, not built too much), then nobody other than the AI agent actually cares about solving your problem (readable, maintainable code) anymore. Or to put it another way, it's only in the agent's interest to solve that problem, for the same reason that today it's in the SWE's interest to solve that problem, rather than the product manager or the business owner.
Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S...
by Fripplebubby on Saturday November 14, 2026 @09:52AM
(#50497487)
> In my experience, Claude is great at producing working code — but whether that code is readable or designed to be easily extensible still requires heavy guidance
AI has already delivered huge productivity gains in my opinion; the whole StackOverflow/Google search part of my life is gone. Instead I get answers from Claude tailored to my specific environment, use-case, problem, etc. Writing well-defined, simple code with lots of prior art in the same repo is easily handed off. But the AI industry and a lot of leadership in big tech seems to be expecting further miracles from AI. Maybe one day a CEO or CPO will just be able to speak their thoughts and a fleet of agents will implement it flawlessly, but we are nowhere near that reality right now.