46 ms·
Tried really hard to avoid the term "hit by a bus" but yes this is exactly what is meant. But looking for something more specific - like, how is that specifica
by uticus 4y ago
Tried really hard to avoid the term "hit by a bus" but yes this is exactly what is meant.
But looking for something more specific - like, how is that specifically planned out in a project? How does being "open source" affect the plan, vs closed?
Or even, what is the specific plan for if Linus gets hit by a bus? Hold a vote? Heir-apparent, decided by Linus himself? Split the responsibilities evenly?
Also, to ask from another viewpoint, what historical case studies are there? Seems like in the open-source community at least everyone is young enough that this hasn't been much of an issue yet.
- eatonphil 4y agoYou give people ownership over bigger subsystems over time, basically.
- lightbendover 4y agoI have rarely seen more than one or two people understand how all those sub-systems work together in any org I have ever been in. So few people look over their own fence.
- baq 4y agoyou can change the name to 'lottery factor' if being hit by a bus is politically impractical at your organization.
- qntmfred 4y agoI've always called it getting hit by the lottery bus
- Mezzie 4y agoI mean depending on the payout for the inevitable lawsuit...
- sebzim4500 4y agoYeah but for many projects the bus factor and the lottery factor can be quite different. Unless your employees are miserable, they will probably still be reachable to answer short form questions after winning the lottery, even if they don't actually work for their full notice period.