Every time you write documentation, consider if it would be less time and energy to fix the problem you're describing instead of apologizing for it. Philosophi

Every time you write documentation, consider if it would be less time and energy to fix the problem you're describing instead of apologizing for it. Philosophical differences between your code and a library you're using are a good example of when you explain rather than fix. But if it's just two chunks of your own code it might just be faster in the long run to make the problem go away instead of having to explain repeatedly why it's there at random intervals. People underestimate the cost of interruptions, and load up their future with self-imposed interruptions.