4 ms·
I would add that people leaving is a cascading failure. One person leaves. That load falls on someone else, leading them to leave too, and so on. "Backfill fast
by panny 5y ago
I would add that people leaving is a cascading failure. One person leaves. That load falls on someone else, leading them to leave too, and so on. "Backfill fast" might seem like the answer, but it compounds the problem when the team that is under greater pressure due to attrition must now stop and work interviews and training instead. Pair that with paranoid managers who decide that now is the time to drop spyware riddled laptops on the whole team, since all the new people are getting them anyway...
The major loss of a team member leaving is the institutional knowledge. They wrote some things that need maintenance and the knowledge on how to do that leaves with them. If I'm an experienced person treading water in a new code base, I may as well get a salary bump by leaving for a new company. Management really doesn't put themselves in our shoes.
- iknowSFR 5y agoIf it’s knowledge centralized to a single employee, then it’s not institutional.
- genmud 5y agoIt is when nobody is left that knows something has been documented in the wiki, source repo or google docs.
- panny 5y agoIt's not centralized to a single employee. It's institutional knowledge that you don't know. All the coders know how to write code. You don't understand the processes that happen in a lumber mill. Now because lumber coder left, you're maintaining code for a lumber mill. You need to learn that stuff, but you've been working in the concrete division of the company. Get it?