Do not be a hero – 3 pros and some tradeoffs
Do not be a hero. Why ? . Ever seen that one guy doing midnight fixes, hot releases after hours and then gets praised in front of everyone making You look bad ? When features are delivered on time and on target the team is considered heroes. We all love rewards and recognition but heroism might become …
Heroes give up work / life balance. As the ancient wisdom teaches us „no good deed goes unpunished”. Whenever there is a new crisis or a target to achieve is set, yesterday’s heroes are quickly forgotten. Long hours eventually might lead to burnout, anxiety and/or even depression.
What “Don’t Be a Hero” Really Means
Do not be a hero. Heroism is kinda an overdrive. Hard to do over long period of time, if You push your engines over the edge You know the consequences. Stuff breaks. Last but not least such events reinforce the false belief
that the resources and methodologies in place are optimal and adequate. If You can sing „I need a hero…” like in Shrek it means that You should look at the problem from a different perspective and acknowledge it. I strongly believe we all should be autonomous and self sufficient in the end.
How to cope with such
Be polite and go for no-hero mode :
- Refusing to be the single point of failure.
- Insisting on planning, automation, documentation, over manual miracles.
- Knowledge sharing sessions so the team always have all the necessary know how.
Pros of Ditching Heroics
- No burnout, keeps sanity: Firefighting leads to exhaustion yet sustainable pace keeps you sharp and ready for years.
- Solid teams: Knowledge spreading and sharing removes a single departure that tanks the company.
- Fewer fires overall: Try „5 whys” for fixing root causes instead of endless „band-aids.”ducktape” solutions.
Cons and Trade-offs
- Boss friction upfront: In hero-worshipping cultures, saying “no” gets you side-eye as “not committed.” To say the least.
- Less instant glory: Heroes snag quick praise and promotions however team players build strong fundaments and are essential.
- Culture lag: If company fixes chaos, you’ll swim upstream solo at first.
| Aspect | Hero Culture | No-Hero Approach |
|---|---|---|
| Short-term wins | Fast fixes, big applause | Slower, steady progress |
| Risk level | High (bus factor 1) | Low (team resilience) |
| Personal toll | Burnout city | Balanced life |
| Scalability | Caps at hero’s bandwidth | Grows with team |
Smart Ways to Go No-Hero
- Document everything: Write runbooks, pair program, review code – raise that bus factor fast.
- Push upstream: Next crisis? Say, “Let’s budget time to fix the real issue, not just patch it.”
- Talk leadership language: Frame it as “building a bulletproof team” not “doing less work.”
Experiment with this over coffee with your crew, pick one idea and spread the load.
Quote to wrap: “Systems outlive heroes.” – Anon engineer wisdom.
Summary, tl;dr
Do not be a hero attitude swaps lone firefighting for shared knowledge, docs, and sustainable teams. Smart companies choose this every time however change always can be painfull at he begining.
Be a hero and safe Yourself first, then help others
Bibliography
- 97 Things Every Data Engineer Should Know (O’Reilly book chapter inspiration)
- Wikipedia – Bus factor (open concept explanation)
