2 ms·
A absolutely love the concept of internal blogging. Writing documentation has a barrier to entry: what if I'm wrong? What if others on my team disagree with ho
by simonw 7y ago
A absolutely love the concept of internal blogging.
Writing documentation has a barrier to entry: what if I'm wrong? What if others on my team disagree with how I'm documenting this? What if I'm on the hook for maintaining this documentation for the rest of my career? Or what if the documentation goes out-of-date and ends up causing more harm than good?
Blogs solve all of these. If I post an internal blog about how something works it has three things that fix this:
1. It has a date on it. It's clear that it may not still be up-to-date in a few years time.
2. It has my name on it. It's clear that this is my opinion / my experience at the time, not the official internal position of the company
3. It's a "blog", not documentation - so it's OK if it's incomplete or inaccurate.
I ran an internal personal blog at my last employer for this reason - using Confluence because we already had it, so I didn't need to introduce a new tool.
I didn't quite manage to make it stick as a habit for other engineers - I'd have liked to invest more effort in that.