3 ms·
I admit, I rarely read documentation of anything, since I have no clue whether to trust it, so I will usually try to just follow my logical thought process of f
by mewpmewp2 3y ago
I admit, I rarely read documentation of anything, since I have no clue whether to trust it, so I will usually try to just follow my logical thought process of figuring out the solution or by trial and error.
This also makes me bad myself at documentation, because if I don't use it I also feel internally that no one would read what I write in the first place also.
Out of responsibility I will try to document shared things, but I never feel productive while doing that, I feel like I am just writing into a void.
- Cthulhu_ 3y ago> I rarely read documentation of anything, since I have no clue whether to trust it There's another big issue with documentation; it's often a write-and-forget thing. I'm confident every team or department should have a full-time documentation owner whose job it is to ensure documentation is up to date, maintained, and verified.
- makeitdouble 3y agoThat happens when you have legal requirement on the documentation. The same way you have an accountant peering over and keeping track of every transaction that happens in your company. Short of that you'll need to explain why the company is losing money because Jim didn't write a full explanation on why his "getUserIdOrNull" function returns null when the user id is not available.
- MetaWhirledPeas 3y ago> I'm confident every team or department should have a full-time documentation owner whose job it is to ensure documentation is up to date, maintained, and verified. I'm not convinced this would work. Such a person wouldn't have time to be a subject matter expert at anything other than the documentation tools. They wouldn't understand what they were writing about.