The Quiet Satisfaction of Good Documentation

Good documentation is most noticeable when I don't have to ask a question. The command is there, the example works and the note explains the odd configuration value. I can get on with the task.

That's the kind I want to leave behind. Short pages with a clear purpose are easier to maintain than an ambitious manual nobody has time to update. When an instruction fails, fixing it is part of fixing the experience of working on the project.