News for hackers. Stuff that matters.
Re:4 Ways to Avoid Institutional Memory Loss When Key Employ... by cydonian_monk on Friday July 28, 2017 @06:24PM (#14878079)
We approach this with documentation (using text / wiki), mentoring, and by trading product responsibilities semi-regularly. There are a few cases where specialized knowledge hasn't changed hands, edge cases, but the cross-training from moving products around has really helped. Also tends to reduce overly-protective ownership of pieces of our product base.

On the downside it means not many are "experts" in their product, and it also drives some folks a bit batty. You'll get into a new product, look at a specific bug, pull a string here or there, and then wonder how the Earth is still in one piece.

Edit: Yet when employees leave there's generally at least one entire team still with us that built or maintained the product who can fill in and help, if needed.

There are no comments on this comment yet.