Last month, my team had a production outage at 9 PM.
I was exhausted. I hadn't slept well in days. My eyes were burning. My back hurt from sitting too long.
My manager asked: "Can you take a look?"
I said yes. Not because I had to. Not because no one else could.
Because I wanted to feel needed.
I fixed the bug at 11 PM. Everyone thanked me. I went to bed at midnight. The next morning, I asked myself: "Why did I say yes?"
The answer wasn't "because I'm a team player." It was darker.
I'm addicted to being needed. And I think you might be too.
How to Know If You're Addicted
You might be addicted to being needed if:
You're the only person who knows how that legacy system works — and you like it that way.
You feel a small spike of anxiety when your team doesn't ask you for help. Not relief. Anxiety.
You've said "yes" to a late-night request when you were already running on empty. More than once.
You secretly feel threatened when a junior developer starts learning your "special" skills. You'd never admit it out loud. But it's there.
Your identity is wrapped up in being "the person who saves the day." You're not just a developer. You're the developer.
You've worked through a vacation. Not because you had to. Because you couldn't stand the thought of things breaking without you.
You feel guilty saying "no" — even when you're already drowning. Saying no feels like letting people down. Saying yes feels like survival.
Read that list again slowly. If you said "oh shit, that's me" to even three of those — keep reading.
What It Actually Cost Me
Here's what my addiction cost me:
Sleep. Weekends. Hobbies. Friends who stopped inviting me out because I always cancelled. A partner who got used to me being "there but not there" — physically present, mentally in a Slack thread.
I told myself I was being dedicated. A team player. A leader.
But the truth is darker: I was feeding an ego addiction. The dopamine hit of "saving the day" was keeping me trapped in a cycle I didn't even recognize as a cycle.
I wasn't helping my team. I was making them dependent on me. And I liked it.
That's the part I'm ashamed to admit.
I wasn't building resilience in my team. I wasn't building scalable systems. I was building a situation where nothing worked without me — and I called that "being valuable."
It wasn't value. It was a cage. And I built it myself.
The Hard Truth Nobody Tells You
Here's what I've learned after a long time of doing this wrong:
Being needed isn't the same as being valuable.
You can be replaceable and still be respected. You can say "no" and still be a leader. You can let someone else fix the bug — and the world won't end.
The companies that "need" you? They'll replace you in a week if you leave. I've seen it happen. You've probably seen it too. Someone who seemed irreplaceable walks out, and somehow, the system keeps running.
The people who love you? They'll still be there after you stop working 80-hour weeks. But only if you don't push them away first.
I'm not saying don't help. Helping is good. Helping is part of what makes this job meaningful.
I'm saying: check your motives.
Are you saying yes because the team genuinely needs you? Or because you need to be needed?
That question changed everything for me.
What I'm Actually Doing Differently
I'm not cured. I want to be clear about that. I still relapse.
Last week, I caught myself saying "yes" to something I should have delegated to a junior dev who was more than capable of handling it. Old habits. They die slow.
But I'm trying small things — not "change your whole life" things. Small, daily things:
1. Pausing before saying yes.
Ten seconds. That's it. Long enough to ask myself one question: "Am I saying yes because they need me — or because I need to feel needed?"
2. Letting junior devs struggle.
Not suffer. Struggle. There's a difference. When I jump in to solve every problem, I steal their learning. When I sit on my hands and let them work through it — they grow. And so do I.
3. Saying "I don't know" — even when I do.
Especially when I do. Breaking the "savior" pattern starts with being willing to not be the answer to every question.
4. Asking myself one question at the end of each day:
"Did I help today because they needed it — or because I needed to feel needed?"
Some days the answer is something I'm proud of. Some days the answer is ugly. But at least I'm asking the question now. That's the difference.
One Question Before You Close This Tab
Be honest with yourself for a second.
When was the last time you said "yes" to work you should have said "no" to?
Not because you had to. Not because no one else could. Because you wanted to feel needed.
If you can't think of an example — great, maybe you've figured this out and I'd love to hear how.
But if an example came to your mind immediately? You're not alone.
I'll share mine in the comments. Your turn.
If this hit close to home, share it with someone on your team who might need to read it. Sometimes the most helpful thing we can do is hand someone else the mirror.
Disclosure: I used AI to help structure and organize my thoughts — but every experience, feeling, and word in this article is my own.
Top comments (6)
Hmm... I think I'm starting to experience something similar, but with GameJam. I've already finished the first jam, started a second, and a third one right now. I think it's a waste of time... Ehhh... I don't know, maybe I should quit? I hope I don't hit the "join" button again while scrolling through the jam feed in the next two weeks!
This is such a real comment.
I've already finished the first, started a second, and a third one right now that's the addiction cycle. One more. Just one more. Then another.
And I hope I don't hit the join button again that's the pull. You know it's probably a waste of time. But something still wants to click.
GameJam should be fun. When it starts feeling like a compulsion, that's when it crosses a line.
I don't know if you should quit. But the fact that you're asking the question? That's noticing. That's the first step.
Thanks for sharing this. 🙌
This took courage to write.
I built the cage myself that line stopped me. Because I've done the same thing. Told myself I was being dedicated, a team player, irreplaceable. But underneath it was fear. Fear that if I wasn't needed, I wouldn't be valuable. Fear that saying no would mean becoming invisible.
The part about feeling threatened when junior devs learn your skills I've felt that too. Never admitted it out loud. But it's there. That quiet voice that says "if they can do it, what's left for me?
You naming it as addiction that's the reframe I needed. It's not dedication. It's not being a team player. It's a pattern. And patterns can be broken.
Thank you for writing this. You're not alone in this. 🙌
Urmila, this comment hit me. 💔
Fear that saying no would mean becoming invisible I've felt that too. And the junior devs part thank you for saying it out loud.
You're right it's a pattern, not an identity. And patterns can be broken. First step is recognizing it. You've already taken it.
We'll learn together. 😊🙌
Great and very honest post! This resonates, not because I'm this kind of dev right now, but previously I went through a phase that certainly looked like it ...
Thank you.
The fact that you can look back and recognize it in your past self that's the win. Most people never even name it. They just keep running the pattern.
Previously I went through a phase that certainly looked like it that's how it works. Slow creep. Then one day, hindsight.
Appreciate you reading. 🙌