> Poorly written or out of date documentation is worse than no documentation.
No, it's not. I _can_ be, but it can also be much better. Documentation is hard, we know that. But it's also incredibly useful in many cases. There are plenty of times where software is nearly useless, or the time required to use it becomes untenable, without documentation.
Honestly, I feel the same way about the code; if you can't be bothered to put a note in a file indicating what it's for (unless it's clearly obvious to a casual observer with limited domain knowledge), then you shouldn't be writing software at all.
If the software cannot be used for its intended purpose without some special knowledge, and that knowledge is not available to everyone who uses that software, then the people who don't have access to that knowledge are going to be unable to use the software for its intended purpose.
To some people in some kinds of organizations, this is a feature. The people with the hidden knowledge are more powerful than those without it.
If the software is written well enough that it doesn't need much or any documentation, then great! If that's not true, though, there had better be documentation if you want people to use it.
Writing good documentation is a skill that takes a non-trivial amount of time to develop. It also takes time to write.
Keeping documentation up to date is hard and takes time/effort.
Poorly written or out of date documentation is worse than no documentation.