Heroes can help fix Hero Worship anti-pattern

I frequently rail against the all-too common anti-pattern of "Hero Worship Culture" in DevOps.  Heroes don't scale.  Hero worship disincentivizes high-quality, reliable software and focuses on heroic efforts to repair bad code.  My litany is long.

Here is an interesting idea articulated in a Basketball analogy that does not always work. The author gives prescriptive methods for the heroes themselves to systematize reactive support, incident management, and DevOps culture.