|
|
|
|
|
by itsronenh
1580 days ago
|
|
I agree with most, if not all, the points raised in the post. I'm curious how people deal with: 1. Organizing knowledge. Too often I've seen a lot of well-written and well-intended information thrown into a shared cloud drive or wiki to rot and grow stale. You end up with multiple, sometimes contradicting documents about the same topic, finding what you're looking for is difficult, and before you know it people revert to tribal knowledge and slack DMs to find out what they need. 2. A writing culture can penalize and demoralize non-native speakers whose writing skills may not be as strong as their peers. I've worked with brilliant individuals who felt like they're perceived as "stupid" because their language skills weren't as polished. |
|
If you have a writing culture, you have management support to not mark work as done until documentation is updated. If someone asks for support because the documentation didn't answer their question, the support ticket is not closed until the documentation's language is improved and clarified. This is usually a good trade-off for management: the time spent keeping documentation up-to-date is repaid many times over by people who are able to help themselves instead of having seniors be continually interrupted. Note that this return is not necessarily realized for very small companies or companies where employee churn is low - this is generally true for large companies and growth-stage companies.
> 2
Companies have a choice, they can: a) decide not to hire people who won't be a cultural fit, b) invest in training to try and align people to the preferred writing culture, c) invest in dedicated roles like technical writers who can sit alongside engineers with poor writing skills, at the gain of being able to hire engineers with poor writing skills, at the cost of additional overhead due to the additional technical writer hire.