I dont. Ive gone down many rabbit holes thanks to, for instance, subtly incorrect or outdated docs in working cultures that valued not being interrupted and it's a recipe for anxiety and a huge waste of time.
I dont think I even had edit rights. I was also under pressure to do my actual job.
I would have loved to have been working in an environment where I could work with the system maintainers to fix their docs collaboratively but alas it was more of an "I'm busy go away" type environment.
I think this type of dysfunction was fairly common during lockdown WFH.
> Hopefully you updated the docs as you encountered them and figured out the most up to date context.
I've been in an environment like this, and it really burned me out.
People broke docs faster than I could fix them, and it was an accepted part of the development process.
My conclusion was that fixing the docs was simply a waste of time. My resulting despair for the software and the company surely destroyed my productivity. (I'm not saying this is a valid excuse; just an explanation.)
> My conclusion was that fixing the docs was simply a waste of time. My resulting despair for the software and the company surely destroyed my productivity.
What did you do instead? It’s certainly frustrating to have people breaking docs that you fixed. But what else is there. You just figured it out on your own and left the docs broken?
> What did you do instead? It’s certainly frustrating to have people breaking docs that you fixed. But what else is there.
I concluded that it was a fatal and unfixable flaw in that community / product / company. This sapped my motivation, and I'm sure resulting burnout was a factor in eventually being laid off.
One thing that sucks about being a senior dev is you're subject to Cassandra [0] syndrome. In a tight labor market, that gets painful.
