The very least you could do is properly quote what I actually said instead of poorly paraphrasing, and then holding that paraphrase up as an example (with a different context). That's no better than putting words in other peoples mouths, its just flawed reasoning, and the tactic comes off as plainly manipulative and biased.
If you read and comprehended what I said, and knew what good documentation practices are, you'd agree if you had the experience.
Every single time I've seen a developer say differently and get their way, its resulted in project cost overruns by integer scaling factors greater than 1, many times in the double digits, assuming the project even completed (some don't).
Availability of good documentation on existing systems makes and breaks project budgets.
I really don't see how you can reasonably think this is a good example, let alone a great example. You of course are free to think what you want.
Fundamentals are covered in Chapter 31 of the Limoncelli books (TPOSA) covers the broad strokes, and Redhat Documentation pre-IBM takeover are examples of good end-product from proper documentation practices.