A sufficiently comprehensive spec is not (necessarily) code
Summary
The article argues that a comprehensive spec is not the same as code, treating specifications as abstractions that define a set of possible implementations. It discusses how formal languages, tests, and even program synthesis relate to specs, and why humans are still needed to craft useful specifications despite advances in AI and LLM-generated code.