You Are Not The Solution: How Good Engineers Become Organizational Debt
The engineer who always figures it out becomes the reason the real fix never gets built. A look at the fixer identity, the competence trap, how careful work becomes invisible, and why 'just say no' is incomplete advice.
There's a pattern I caught in myself: a casual Slack message comes in, and before I've finished reading it I'm already calculating how to clear Thursday afternoon to do it. The gap between "can I do this?" and "should I do this?" is where a lot of capable engineers quietly disappear. The concrete version: I fixed a production issue with manual database surgery, said "we need an endpoint for this," and two weeks later 300 users needed the same fix, the endpoint still didn't exist, and a PM asked me to "run the script again."
Key takeaways
- If being the fixer is your identity, declining a request briefly suspends the person you think you are: that's why you say yes after seeing the pattern
- Careful work goes invisible because it's done well: people see the outcome, not the double-checking; effortless-looking things don't feel like they need a system
- Filling the gap removes the pressure that would force someone to close it: you're helping justify never building the thing
- "Just say no" is downstream of the problem: reframe ("we're treating an emergency workaround as a permanent workflow") and redirect ("here's what we should do instead and how I can help")
- When I finally held the line, the API got built weeks later: remove the person filling a gap and it becomes a ticket; people only fix what they can see
Who this is for
Senior engineers who built their reputation on reliability and are starting to feel a quiet irritation when certain requests come in. Engineering-career essay.
The full piece is on Medium.