I've had to use outdated documentation that made the problem worse. So I guess bad documentation is like bad, unprotected sex with a lot lizard that leaves you with an itching or burning sensation.
Absolutely not. I'd rather have no documentation and start from scratch than be gaslit by an entire team of people telling me that the very obviously wrong documentation is correct and has been correct for 30 years
Respectfully disagree. Sometimes the documentation is so bad that you have more questions than answers and even then, what they provide still doesn't really explain how to do something with enough details. It's all literally shot in the dark and you're just left with leap of faith. * cough * Sonicwall * cough *
Last week I spent a day trying to figure out why the thing in the damn documentation doesn't work.
Turns out, for that project "latest" doesn't point to their latest release, but to what they currently have on their dev branch. And apparently they changed the whole module around since the last release.
Maybe it can be translated into something else, like, "Documentation is like toilet paper, when it's good it's good, when it's bad it's better than nothing"? Or, "Documentation is like clothes, even if they are bad it's better than nothing", or "Documentation is like having something you need, it's better to have the thing you need even if is not good, than to not have the thing you need at all"?
I like the analogy with toilet paper.
Because when its bad, the very thing that was supposed to help you, got you covered in shit with no back out plan, making it that much worse.
Just consider most people really like sex, and some experience it as a very intense physical want to the point it makes sense that a bad version of it is better than none at all. Sort of similar to food. Better to have bad-tasting food and at least sate your hunger than to have nothing and starve.
Although, of course, it breaks down. The comments talk about actively harmful sex people wouldn't want as well as harmful documentation; bad sex and documentation is not actually always better than no sex or no documentation. In the analogy, this would be sex that gives you an STD, or documentation that sends you running in circles and misleads you.
I've found a lot of understanding sex comes with just understanding a lot of people really really want it and experience it as a nigh-on need. Maybe liken it to some intense desires you have, things you need to be happy that you nonetheless don't need to survive. (Of course, this is a generalization, I understand not all people with sexual desires have them this intensely. Some don't need it to be happy but would sure like it a lot. And some might even get it more mildly. But for the purpose of understanding more mainstream jokes, analogies, etc. about sex…)
When documentation is missing critical bits of information I don't know if its better than nothing. Spend ages and then have to raise a ticket saying its a bug because its not working as documented, when no documentation would have just been an instant ticket raised asking how its supposed to work. Because it turns out everything was working correctly and the customer had just set something up wrong but there was no documentation covering that bit so according to what we had, all looked good.