(no title)
prpl | 13 days ago
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.
prpl | 13 days ago
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.
josephg|13 days ago
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.
don_esteban|13 days ago
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.
bavell|13 days ago
I'd much rather have a conversation with them to discuss their current problems and workflow, then offer my ideas and solutions.
iwontberude|13 days ago
baq|13 days ago
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.
avmich|12 days ago
la64710|13 days ago