Spec-driven development doesn't work if you're too confused to write the spec

The article argues that spec-driven development assumes clear understanding of the domain, but often developers are too confused to write precise specs because understanding evolves through the process. It differentiates between domain logic, which is conceptually constrained and crucial, and representation management, which involves arbitrary yet binding technical decisions. Unlike assembly language abstraction, high-level code acts closer to an unambiguous spec, but writing that spec is a discovery process requiring deep domain insight. The future likely involves better specification languages and tools to separate pure domain logic from representation details, improving programming efficiency.