Ego Is the Voice That Says You Don't Belong
There's a voice in your head that has probably killed more good ideas, stalled more careers, and broken more relationships than any external obstacle ever could.
It tells you that you're not ready. That other people know more. That you'll be found out eventually. That speaking up is risky. That admitting you don't know something is dangerous.
That voice is your ego. And it was built to protect you.
Where the ego comes from
The ego isn't a character flaw. It formed in childhood as a set of coping mechanisms, built to keep you safe and accepted by the group around you.
And for most of human history, social acceptance wasn't just nice to have. It was survival. Standing out, being wrong, or showing weakness in a tribal setting had real consequences.
The ego is like our preference for fatty food. In the caveman era, calories were hard to find, so the body learned to crave them. We're still wired that way. We just haven't caught up.
The ego is the same kind of leftover wiring. It was useful once. Now it mostly gets in the way.
You can't be angry at it. But you do need to learn how to stop letting it run things.
How it shows up in tech specifically
In the tech world, ego tends to wear a very specific disguise: the need to sound smart.
Developers love to prove they know every data structure, every design pattern, every algorithm running time. They use big words in meetings. They make simple things sound complex. They give answers they're not sure about rather than admit they don't know.
Ego talking:
Someone asks if you're familiar with a part of the codebase you've never touched. You give a vague, half-confident answer rather than say you don't know it.
Authentic response:
"I'm not familiar with that part of the system. Give me a bit of time to get up to speed and I'll get back to you."
The second answer is more honest, more useful, and more respected. That last part is the one your ego can't accept.
The person asking didn't need you to know everything. They needed a real answer.
The imposter syndrome loop
There's a mindset a lot of developers carry: they aren't a "real" developer until they've done X. Until they've shipped Y. Until they know Z.
The problem is X never comes. The industry moves too fast. You learn something and it changes. You ship something and the next challenge is already waiting.
There is no morning where you wake up and feel like you've arrived. That feeling isn't coming. And waiting for it before you step forward is a trap.
What makes a developer valuable isn't knowing every algorithm. It's communication, ownership, clarity of thought, and the ability to design something that works for the people who have to use it.
Your hunger to learn. Your openness. Your ability to navigate ambiguity and work well with other people. Those things make you valuable. Not whether you can recite a heap implementation from memory.
Three steps to start taming it
01 Read this book first
About 200 pages. Short enough to read in a weekend, dense enough to sit with for months. It will be uncomfortable to read because your ego will tell you it doesn't apply to you. That discomfort is exactly why you need it. Start here.
02 Observe it. Don't fix it yet.
Once you know what you're looking for, spend a few weeks just noticing.
Make mental notes when ego shows up:
- Which person at work triggers it most?
- What situations make you feel defensive?
- When do you talk more to fill silence than to communicate?
- When do you give an answer you're not sure about instead of saying you don't know?
- When do you use jargon to feel smart instead of to be clear?
Don't try to change yet. Just collect data. Trying to fix everything at once is overwhelming, and overwhelming yourself is how people quit.
03 Slowly modify one behavior at a time
Pick the pattern you notice most and work on that one first.
If there's one person at work who consistently brings out your ego, that's the place to start. Ask why. Is that person also communicating from their ego? Are you both just defending yourselves instead of actually talking?
Try showing some vulnerability with them. Tell them you don't know something. Disagree directly instead of talking around it. See what happens when you stop trying to win the conversation and start trying to have one.
A lot of communication breakdowns in tech teams are just two egos talking past each other, both afraid of the same thing.
What you're actually trying to build
This isn't about becoming someone who never has an opinion or never pushes back. Strong communication means the opposite of that.
It means speaking clearly to your actual audience. Using language they can follow. Saying what you mean without needing to impress anyone. Being honest when you don't know something. Owning mistakes instead of deflecting them.
Those habits compound over time. People start to trust you. They come to you with problems. They advocate for you in rooms you're not in.
The voice telling you that you don't belong? It's just an old alarm that forgot it was no longer needed. You can acknowledge it and walk past it anyway.