> A "hero" project is one where 80% or more of the contributions are made by the 20% of the developers.

If that 20% leave, the other 80% would contribute equally or the ration 20/80 will be preserved?

This seams a feedback loop. Once a developer has written more code than others is in a better position to write even more. If that is the case "hero developer" is a floating position, depending so much on your skill and how much time you have been working in a project and other circumstances.

> Organizationsshould reflect on better ways to find and retain more ofthese software heroes.

I had this discussion recently. If you create a team of "heroes" all become way slower than when they were in different teams.

My personal conclusion, and the way of working that I try to implement at work is that small independent projects allow for developers to be fast and reliable. If your project is correctly divided, anyone can contribute ( at their level of expertise). If you have a big complex projects then old-timers that created originally the code are the only ones that can work with it efficiently if no other developers make big changes (reducing the ability of other developers to contribute independently of their level of skill).

So, before going in search of "heroes" think if your projects are correctly divided. And think about the risk that you create when a "hero developer" is needed and leaves.