A sufficiently comprehensive spec is not (necessarily) code

The article argues that a comprehensive specification is not necessarily code, as a spec corresponds to a set of possible implementations while code is a single implementation. Specifications are abstractions of code, and even detailed specs that can generate programs remain distinct from code itself.