2 ms·
For the benevolent dictator, they surround themselves with like-minded lieutenants (not the coup d'etat-inclined, but mutual respect and trust kind). But for s
by neilv 4y ago
For the benevolent dictator, they surround themselves with like-minded lieutenants (not the coup d'etat-inclined, but mutual respect and trust kind).
But for software engineering in general, you want a culture of people focused on working as a team towards the mission, not on individual metrics/career. This affects what you do, how you to it, how you document it, how you make decisions, etc. If there's no immediate plan for what to do when the lead dev not available, they'll figure it out.
- neilv 4y agoBut, if you don't have trust in your engineering/product org (e.g., working as a team rather than for individual metrics is seen as counterproductive for individual career, execs not trusted, documenting is seen as making you expendable in headcount reduction, etc.)... then either fix your org culture or move to somewhere where you can have a better culture, IMHO. (And if SHTF before you fix culture or move, then the question of succession for a lead dev can just be bumped up the management hierarchy at that time. And the interim solution can be creative based on the details of the immediate situation. For example, there might be an obvious successor, based on their background, skills, and availability at that moment, and the nature of that might determine whether to be thinking of them as interim, provisional, or long-term.)