Re:The Perks of a High-Documentation, Low-Meeting Work Culture
by Viliam1234 on Tuesday November 22, 2022 @06:42PM
(#33713148)
> The last thing I want is to raise the friction for writing down documentation.
A better solution might be that anyone can write the documentation, and there is a maintainer who constantly refactors the wiki to keep it legible. Makes sure the information is not duplicated, adds hyperlinks to things, etc.
Re:The Perks of a High-Documentation, Low-Meeting Work Culture
by wankle on Tuesday November 22, 2022 @10:55PM
(#33714991)
Internal documentation is everyone's responsibility, not a "tech writer". External should be written by a professional, agree.
Re:The Perks of a High-Documentation, Low-Meeting Work Culture
by Viliam1234 on Wednesday November 23, 2022 @12:06PM
(#33721748)
"Everyone's responsibility" sounds like an euphemism for "no one really cares". When people actually care about something, they hire an expert.
Why do you hire software developers, instead of making software development everyone's responsibility? Is that because most people suck at software development? Well, most people suck at writing documentation, too.
Re:The Perks of a High-Documentation, Low-Meeting Work Culture
by Aeolun on Tuesday November 22, 2022 @06:32PM
(#33713059)
I mean. I guess? The difference between having it written down in Confluence and disappearing into the ether is academic though. Either way nobody will ever find the information again.
It's hard enough to get technical minded people to contribute to a git (or style) based knowledge base.
Pick your poison I guess but I'm quite happy to have testers/BAs/directors/etc able to quickly jot down thoughts roughly than have it disappear into the ether.