> > If something can be misunderstood, it will be.
> There are two ways to read documentation: trying to find the worst
> possible interpretation and trying to find the best possible
Yes, and the writer should always read it trying to find the worst possible
interpretation. That is the burden you need to assume, if you want to
Why? Because that is how you improve communication. Progress comes through
If you as a writer read only what you intended to say, and not what you
actually wrote, with all of its reasonable possible interpretations, then
you are not putting yourself in the place of the reader. And you write _for
This is no different from writing code. The reader is your compiler or
interpreter: it is s?he who lets you know if what you wrote makes sense.