I’m finishing up documentation for our new server product, and added a ‘Troubleshooting’ section to address some common problems and solutions. Riddler wants to see the final manual before it goes to print so I show him a copy, prompting the following discussion:

Riddler:
Troubleshooting info should be on the web, not in the document.
HPDEB:
Yes, but it should also be in the document. We’re asked about these issues so frequently that we should cover them where to can to avoid repeated questions.
Riddler:
Ok, but put it on web as well. But hide it so nobody can find it unless they have the print document.
HPDEB:
Why?
Riddler:
So people can’t see that there might be problems with the product.

Obviously the purpose of technical documentation is to communicate only that we are brilliant and infallible.

He’d rather make it difficult for a user to get an answer instead of communicating that we respond to issues. He’s nearly mastered his ostrich head-buried-in-sand technique.