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
I think there’s a difference between bad and wrong. Wrong documentation is incorrect. Bad documentation isn’t really incorrect, it’s just poorly executedb and mostly unhelpful.
Wrong documentation is still a pretty big problem, even without the gaslighting. Incomplete documentation is better than none; incorrect documentation is not.
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
I think there’s a difference between bad and wrong. Wrong documentation is incorrect. Bad documentation isn’t really incorrect, it’s just poorly executedb and mostly unhelpful.
I mean, incorrect documentation is clearly bad, so…
Seemed more like the problem was the gaslighting than the documentation.
Wrong documentation is still a pretty big problem, even without the gaslighting. Incomplete documentation is better than none; incorrect documentation is not.
I can name a few examples of this
That documentation sounds like marriage.
You ok?
Well also like sex, when it’s really bad it’s worse than nothing.