> The strategy is to hire enough and be managed to a degree such that the operation of any single system is never left leave to any single engineer. In code th

> The strategy is to hire enough and be managed to a degree such that the operation of any single system is never left leave to any single engineer. In code the equivalent of this is having some bloated thing that's been touched by one too many shitty people who are only willing to learn just enough to mark their tickets done. That code turns into a ball and chain that no one wants to work on. Turnover becomes normalized One of the reasons why most important stuff happens in open source