What a Useful Specification Has to Do
A useful specification must compress intent, supply the right context for the current decision, and learn from code without becoming a copy of it.
9 min read
4 entries
A useful specification must compress intent, supply the right context for the current decision, and learn from code without becoming a copy of it.
Twelve years ago a strict red-green-refactor ritual carried me to a solution I didn't know how to design. The trick wasn't thinking harder. It was thinking on schedule.
To know whether specification-driven development works, I first had to ask what a specification is supposed to do.
What this notebook is for, and why the name sounds like a spell.