If I don't document something, it's usually either for a good reason, or a bad reason. In this case it's a good reason. :-)
About this quote
- What does it mean?
- Skipping documentation is either justified or not; here it is justified.
- In plain terms
- I don't document only when there's a good reason, and this is one.
- What can you take from it?
- Document when it adds value; otherwise, be transparent about omission.
Where it applies
Putting it to work
Questions to consider
- When is it acceptable to skip documentation?
- How do you communicate the reason?
Another view
What seems a good reason to one may be seen as neglect by another.
More from Larry Wall
If you want to see useful Perl examples, we can certainly arrange to have comp.lang.misc flooded with them, but I don't think that would help the advance of ci…
Permalink to quote #50 Down that path lies madness. On the other hand, the road to hell is paved with melting snowballs.
Permalink to quote #48 > (It's sorta like sed, but not. It's sorta like awk, but not. etc.) Guilty as charged. Perl is happily ugly, and happily derivative.
Permalink to quote #51
Related quotes
I spent this time polishing up the software/hardware documentation, renaming registers to be more meaningful. This was actually time well spent in my life.
Jay MinerJay Miner quote #3 It's documented in The Book, somewhere...
Larry WallLarry Wall quote #14 Let's say the docs present a simplified view of reality... :-)
Larry WallLarry Wall quote #17