# No capes: the perils of being a hero-engineer

DevFeed: [No capes: the perils of being a hero-engineer](<https://devfeed.tech/articles/no-capes-the-perils-of-being-a-hero-engineer-11934.md>)

Original publisher: [Read original article](<https://incident.io/blog/no-capes>)

Author: Isaac Seymour

Published: 2022-01-31T00:00:00Z

Content type: opinion

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [Incident response](<https://devfeed.tech/topics/incident-response.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [pull-requests](<https://devfeed.tech/topics/pull-requests.md>)

Tags: [communication](<https://devfeed.tech/tags/communication.md>), [customers](<https://devfeed.tech/tags/customers.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [slack](<https://devfeed.tech/tags/slack.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>)

## AI overview

The article argues that relying on hero-engineers to handle every emergency creates stress, discourages broader learning, and concentrates incident knowledge in private conversations. It recommends open communication, wider participation, and clear incident leadership so teams can collaborate while engineers focus on resolving problems.

## Source excerpt

When I first started out as an engineer I really leant in to being a hero-engineer; here's the advice I wish I'd listened to earlier. you want to avoid.