"I guess the dream is that we'll all become business founders, with the LLM as our founding engineer, and we can just ask them to build what we think the busine

"I guess the dream is that we'll all become business founders, with the LLM as our founding engineer, and we can just ask them to build what we think the business needs, and go through them to make refinements and changes." That's pretty much what I'm doing after 20+ years of writing code. They do feel like teammates sometimes, though I tend to give them much more explicit instructions. It feels less like complete outsourcing and more like declarative programming in English. Where we differ is that you seem to see code as this rigorous medium of thought that defines the craft, whereas I don't. I've always viewed code as a translation layer between human intent and machine execution. That layer has simply dissolved. Viewing code this way might feel less romantic and more pragmatic, but I think it’s more accurate. You can think, reason, and make decisions just as rigorously in plain English. The skill of translating English into code was what got automated—the true craft lives way above and beyond that layer. But I don't think I can convince you on HN if you have such a strong views on coding. And I'm left to wonder, how are you feeling about the craft if what you perceived as the core activity (I thinking coding was at best 20% of the craft) got fully automated? Have you tried to build a really complex software with LLMs over few months? I think that might give you more clear picture of what truly happened.