Devops
Useful Devops tips.
Documentation
Below is primarily taken from https://documentation.divio.com/, posted in Hacker News here. All technical documentation falls under one the following four (4) groups.
- Tutorials: Learning oriented
- How-to guides: Problem oriented
- Technical reference: Understanding oriented
- Explanation: Information oriented
These 4 groups form a quadrant where each of the components is similar to its two neighbours:
- tutorials and how-to guides are both concerned with describing practical steps
- how-to guides and technical reference are both what we need when we are at work, coding
- reference guides and explanation are both concerned with theoretical knowledge
- tutorials and explanation are both most useful when we are studying, rather than actually working
Recognizing above breakdown will help add structure to your documentation.
Other useful pointers:
- One useful Hacker News discussion comment was the reference to using the “SEE” method (Statement, Example, Explanation).
- Also, include an Introduction, Summary and a Rationale (including alternate solutions) works for a document is of essence.
- Steven Pinker’s eminent point on why there is so much bad writing: the curse of knowledge, or knowing so much about a subject that you totally forget your readers are not as familiar.
Finally, be concise!