Your Reaction Is The Bug
Stop Letting Bad Feedback Turn You Into Someone You're Not
Between the Slack notification and your angry reply, there is a gap. In that gap lives your entire career trajectory.
Your PR just got torn apart. Not gently, either. Someone went line by line, questioned your architecture, and did it in a public channel where half the team can see it. Your face goes hot. Your fingers are already moving toward the keyboard. You’ve got a response locked and loaded, and it starts with “Well, actually...”
Stop. Don’t send it.
I’ve been there. Early in my career, I’d fire back almost immediately. I was convinced that defending my code was the same thing as defending my competence. Looking back now, I can’t even remember what half those arguments were about. The thing that felt like a five-alarm crisis on a Tuesday afternoon? Gone from my memory entirely. But the reputation I was building, that part stuck around a lot longer than the debate.
Here’s what Epictetus figured out a couple thousand years before Slack existed: events themselves are neutral. It’s our judgment about them that creates the suffering or the peace. Your PR getting reviewed isn’t an attack. It’s a process. The attack is a story your brain invented in about 300 milliseconds flat.
Your First Reaction Is Almost Always Wrong
That defensive surge you feel when someone questions your technical decision in front of the team? That’s not your professional instincts kicking in. That’s evolutionary firmware running on code that was written for a very different threat environment. Your nervous system genuinely cannot tell the difference between a critical comment on a pull request and a predator in the bushes. It fires the same way either time.
The Stoics called this the “first impression”, the automatic, unchosen reaction that happens before your brain has had time to actually think. The goal isn’t to kill that reaction. You can’t. The goal is to create a gap between the impression and your response, and then actually use that gap.
Even three seconds is enough to shift from defensive to curious. That sounds insultingly simple, and it is. But simple doesn’t mean easy. The pause is a trained skill, not a personality trait. And most of us have spent years training the opposite habit.
The Story You’re Telling Yourself
When someone pushes back on your technical decision, your brain immediately starts constructing a narrative. It’s not just processing the feedback; it’s assigning motive, predicting consequences, and scoring the whole thing against your sense of self-worth. By the time you’re ready to respond, you’re not responding to the comment anymore. You’re responding to the movie your brain made about the comment.
So before you fire off that reply, ask yourself one question: what else could this mean?
What if they’re trying to prevent a production bug? What if they caught something you genuinely missed? What if they see the codebase from a different angle? Not a better angle, not a worse one, just different. And that perspective is actually useful to you?
Maybe you introduced a feature that already exists somewhere else in the codebase and someone’s pointing it out. That’s not an insult, that’s someone doing their job. The difference between receiving that as an attack versus receiving it as information is entirely in your head.
And entirely in your control.
The Practical Tools
The Stoics weren’t just philosophers. They were incredibly practical. Here are three things that actually work:
The draft folder rule. Before you hit send on that “well actually” message, save it as a draft and come back in an hour. You’ll delete 80% of them. The other 20% you’ll rewrite into something that doesn’t make you look like an asshole. This works for social media too. Write the response, feel the satisfaction of having written it, then let it sit. Most of the time, it never needs to leave your drafts.
The three questions. Before reacting, run the comment through a quick filter: Is my interpretation actually true? Is my response necessary? Is it going to move things forward or just make me feel better for thirty seconds? Most knee-jerk reactions fail at least one of those tests. Usually all three.
The timeline check. Will this matter in ten minutes? Ten months? Ten years? I’ve lost sleep over feedback that I legitimately cannot recall today. That’s not me being zen about it, that’s just how it played out. The things that feel like career-ending disasters during a sprint rarely survive contact with next week’s stand-up.
Emotions Are Data, Not Orders
Getting angry about a management decision or a brutal code review tells you something real about your expectations and your values. That’s useful information. It’s not a command to act on the anger.
Stoics feel emotions. They’re not robots. They just don’t take orders from them.
There’s a time to push back and a time to let it go. Not every technical decision is worth the argument. Sometimes the smarter move is to take the feedback, consider it honestly, and ask whether your approach was actually the right one. Sometimes you’ll decide it was and you’ll make that case clearly and calmly. Sometimes you’ll realize they had a point you missed. Both outcomes are fine. Neither of them requires you to go to war in a Slack thread.
The Gap Is the Whole Game
Change is the one constant in this field. Priorities shift mid-sprint. Architecture decisions get revisited. Someone’s going to question your code in a public forum again, probably next week. That’s not a bug in the system. That’s the system.
What separates the developers who grow through that process from the ones who get ground down by it isn’t talent or experience. It’s the ability to create that gap. Act between the notification and the reply. Shape your impression into a thoughtful response.
Your career isn’t built in the moments when everything goes smoothly. It’s built in the moments when someone tears your PR apart and you respond like a professional instead of a cornered animal.
The gap is where that happens.
Quote of the Day:
“It’s not what happens to you, but how you react to it that matters.” - Epictetus
👉 If you enjoy reading this post, feel free to share it with friends!
Or feel free to click the ❤️ button on this post so more people can discover it on Substack 🙏
You can find me on X and Instagram.
Also, I just launched a new YouTube channel - Code & Composure