The first part is making sure you built to your specification, the second thing is making sure you built specification was correct.
The second part is going to be the hard part for complex software and systems.
I don't know about you, but I'd much rather be shown a demo made by our end users (with claude) than get sent a 100 page spec. Especially since most specs - if you build to them - don't solve anyone's real problems.
Demo, don't memo.
Demo for the main flow is easy. The hard part is thinking through all the corner cases and their interactions, so your system robustly works in real world, interacting with the everyday chaos in a non-brittle fashion.
Lol I've been programming for 30 years.
> The complexity of these systems is crazy. Unless he meant ah HTML text area with "save" button - then sure, why not.
What do you see as the difference between an LLM making an HTML text area and a save button, and an LLM making MS word? It just sounds like a scaling problem to me. We've been scaling computers since long before I was born. My first computer was a 386 with 4mb of ram. You needed a special add-in chip to enable floating point calculations. Now look at what we have.
As far as I can tell, the only difference between opus 4.6 and some future AI model that could code up MS word is a difference in scale. Are you betting against the entire computing (software and hardware) industry being unable to scale LLMs past their current point? That seems like a really bad bet to me. Especially seeing how far they've come in the last few years. Claude code can already do some quite complex tasks. I got it to write a simple web based email client for me yesterday. It took about an hour in total. It has some bugs, but the email client works.
We scaled hard drives. We scaled down silicon chips. We scaled digital camera sensors. And display resolutions. And networking bandwidth. We went from the palm pilot to the first iphone to modern phones. Do you really think we'll be unable to scale AI models?
I'd much rather have a conversation with them to discuss their current problems and workflow, then offer my ideas and solutions.
Not going to. Is. Actually, always has been; it isn’t that coding solutions wasn’t hard before, but verification and validation cannot be made arbitrarily cheap. This is the new moat - if your solutions require time consuming and expensive in dollar terms qa (in the widest sense), it becomes the single barrier to entry.
