Armstrong: I like documentation. I don't think a program…
““Armstrong: I like documentation. I don't think a program is finished until you've written some reasonable documentation. And I quite like a specification. I think it's unprofessional these people who say, "What does it do? Read the code." The code shows me what it does. It doesn't show me what it's supposed to do. I think the code is the answer to a problem.””
About This Quote
This interpretation was drafted with AI assistance. It is one reading of the quote, not the author's own explanation.
Good documentation and specifications are essential because code alone cannot convey intent or design, ensuring clarity and professionalism.
In simple terms: Documentation explains what code should do, not just what it does.
Key Takeaway
Write clear docs and specs.
Themes
software development
professionalism
clarity
communication
Mood
pragmatic
analytical
professional
Type
Documentation:1
Programming:1
Technology:1
Like Documentation:1
Documentation Quite:0
Code Answer:0
Reasonable Documentation:1
When to use this quote
- team onboarding
- code reviews
- maintenance
- client handoffs
Key Concepts
technical writing
software engineering principles
documentation standards
Questions to Reflect On
- Why is documentation vital for future developers?
- How do specs improve code quality?
A Different Perspective
Overemphasis on docs can slow rapid prototyping.