How adults handle disagreement, grow their careers, and stop embarrassing themselves in public
There’s an awkward truth that almost nobody wants to hear, but you see it every day in technical careers:
Your long-term career has far less to do with the next technology you learn than with your ability to read and write like an adult.
Not just decoding words. Not just firing off clever replies. I mean, actually understanding what’s being said, especially when it challenges your beliefs, your assumptions, or your ego, and then responding in a way that moves the conversation forward instead of blowing it up.
You’ve seen the pattern:
Someone reacts furiously to a post they clearly didn’t finish reading.
People jump into a comment thread to “correct” something that was explicitly addressed two paragraphs earlier.
A colleague storms into a design review, talks for twenty minutes straight, and somehow misses the core problem everyone else is trying to solve.
An engineer receives written feedback, ignores the key points, and responds with an essay defending things nobody actually attacked.
In all of these cases, the same thing is happening: the person isn’t engaging with the actual content. They’re reacting to how it makes them feel.
And here’s the part that stings:
When you do this repeatedly, it doesn’t reveal anything profound about the post, the document, or the other person. It reveals a lot about you.
People notice. Especially the people deciding who gets promoted, who gets trusted, and who gets invited into serious conversations.
Let’s talk about why this happens, how it quietly wrecks careers, and what to do instead.
Reading Isn’t Just Decoding Text; It’s Managing Your Ego
Most professionals can “read” in the basic sense: their eyes move across the lines, they understand individual sentences, and they can quote fragments back.
But professional reading is a different skill.
Professional reading is what happens when you open a design doc, a post, an RFC, a PR/FAQ review, a 6-page, or a feedback email, and you’re able to:
Understand the core message and the intent behind it.
Recognize where it challenges your mental model, and sit with that discomfort.
Separate “this annoys me” from “this is wrong.”
Ask yourself whether you might be missing context or nuance.
A surprising number of people never make it past the first step. They read just enough to find something that triggers them, then they stop reading and start reacting.
You can see it in how they respond:
They dismiss a post or thread with, “This is nonsense,” without engaging with the actual argument.
They cherry-pick a sentence and ignore all the caveats surrounding it.
They latch onto a side remark and argue about that, while the main point sails over their head.
They reply with a wall of text that sounds impressive but doesn’t connect to what was actually written.
What’s going on under the surface is simple: their ego is doing the reading.
Instead of processing, “This is a perspective I don’t share; let me understand it,” the internal translation is: “This text is attacking my identity; I must defend myself.”
When that switch flips, you’re no longer reading the text. You’re fighting a battle in your head, and the words on the screen become background noise.
From the outside, this doesn’t make you look passionate or principled. It makes you look:
Insecure
Narcissistic
Difficult to work with
Unable to handle being challenged
And that is catastrophic for your career, whether you admit it to yourself or not.
The Narcissistic Trap: When Being Right Matters More Than Learning
Let me set the tone here: disagreement is healthy. Strong opinions are useful. Pushback is necessary. You absolutely should challenge bad ideas, flawed designs, and sloppy thinking.
But there’s a difference between disagreement in the service of truth and disagreement in the service of ego.
You fall into the narcissistic trap when:
You can’t stand being challenged by facts, data, or lived experiences that don’t match yours.
You treat every discussion as a chance to impose your view rather than refine it.
You feel personally attacked when someone critiques your idea, document, or design.
You believe that if you don’t “win” the exchange, you’ve somehow lost status.
This isn’t just stubbornness. Stubbornness is digging in on a specific point. The narcissistic trap is deeper: it’s the inability to grasp a simple message because everything you read is filtered through “what does this say about me?”
So you read a post about a different way to run operations and think, “They’re saying I’ve done everything wrong.”
You read a design doc that proposes retiring an old pattern you like and think, “They’re attacking my legacy.”
You read feedback suggesting you improve your communication and think, “They’re disrespecting my intelligence.”
In each case, the actual content becomes irrelevant; everything is interpreted as a personal affront.
The tragedy is that this behavior blocks growth. You can’t learn from reality if every piece of input that doesn’t flatter you gets rejected on arrival.
And in technical careers, reality is unforgiving. Systems break. Data contradicts your theories. Users behave differently from what you predicted. Designs you loved don’t scale. If you can’t absorb and integrate that feedback, you get stuck; louder, maybe, but not wiser.
When You Miss the Point Professionally: Real Damage to Your Career
Let’s move from abstract psychology to very practical career consequences.
Imagine you’re in a design review. Someone shares a thoughtful document that lays out the problem, constraints, trade-offs, and the recommended approach.
If you skim a few paragraphs, pick one detail that annoys you, and then speak for ten minutes about that detail while ignoring the main problem, here’s what everyone hears:
“This person doesn’t read carefully, doesn’t listen, and cares more about hearing themselves talk than about solving the problem.”
You may think you’re showcasing your brilliance. What you’re actually showcasing is your unreliability.
Or imagine you’re in a code or document review:
You ask questions already answered in the text because you didn’t read to the end.
You nitpick word choice but ignore serious design flaws.
You argue with a strawman version of the proposal that bears little resemblance to what’s written.
Others might not confront you directly, but they remember. Over time, a quiet consensus forms around you:
“They don’t pay attention.”
“They’re exhausting to work with.”
“They always make everything about them.”
“We can’t trust them with high-stakes communication.”
Now think about written feedback: performance reviews, peer feedback, mentor advice.
If your pattern is to respond with long, defensive essays that never once say, “I see your point,” or “You’re right, I need to work on this,” managers notice. Even when you are right about some aspects, your inability to acknowledge valid parts of the message becomes the headline.
At senior levels, that’s a killer. Senior roles are not given to people who are merely technically strong. They’re given to people who can read a room, read a doc, read a situation, and respond with clarity, humility, and focus.
If you consistently “miss the point,” you don’t get those roles, no matter how smart you are in your own head.
Writing Like a Professional: Less Rant, More Signal
The other side of this coin is how you write.
It’s very easy to type in a way that feels powerful to you but lands terribly on everyone else: sarcastic replies, “mic drop” comments, snarky one-liners, “let me educate you” essays.
Those might get you some likes from people who enjoy the drama. They don’t get you trust from people who actually make decisions.
Professional writing, especially in technical environments, isn’t about showing off. It’s about moving work forward:
Clarifying a problem in a way everyone can understand.
Summarizing complex tradeoffs so the team can make a decision.
Responding to disagreement in a way that tightens the argument instead of blowing up the relationship.
Compare these two reactions to a document you disagree with:
“This is completely wrong. You’re ignoring obvious facts. I don’t know how you came to these conclusions, but they make no sense. Here’s the correct way to think about it…”
vs.
“I read the doc and I see the direction you’re going. I have a different view on X and Y based on [this data / these incidents / these constraints]. Let me walk through where I’m aligned, where I’m not, and what I think we might be missing.”
Both can contain strong disagreement. One invites a fight. The other invites a conversation.
The first may feel cathartic to write. The second builds credibility.
Some people love to “talk the hind legs off a donkey” while staying completely disconnected from reality. That’s exactly what verbose but low-signal writing looks like:
Endless words, very little listening, and no actual engagement with the core issue.
The antidote isn’t to write less; it’s to write with discipline:
Did I understand the original point correctly?
Am I responding to what was actually written, not what I imagined?
Am I adding insight, or just venting?
If someone skimmed my reply, would they understand my core argument in a sentence or two?
Professionals write for their readers, not for their ego.
Practical Reboot: How to Read, Think, and Respond Like a Senior
So what does it look like to behave differently in practice?
Start small. The next time you’re about to react to a post, doc, or message that irritates you, try this sequence:
First, finish reading.
Not “skim until annoyed.” Actually read the whole thing. If it’s long, take breaks. But do not respond until you’ve seen the entire argument.
Second, restate their point in your own words.
Before you reply, ask yourself: “If I had to summarize their main argument in two sentences, what would I say?” If you can’t do it, you’re not ready to respond. You’re reacting to fragments.
If it’s an important conversation, consider literally starting your reply with a summary:
“If I understand correctly, you’re saying X, Y, and Z. Let me know if I’m misrepresenting anything.”
This is not a weakness. It’s professionalism.
Third, ask “What am I missing?” before you ask “How is this wrong?”
Look for hidden constraints, context, or goals that might explain their position. Maybe they have data you don’t. Maybe they’re designing for users or environments you haven’t dealt with. Maybe they’re optimizing for a different failure mode.
Even if you still disagree, your response will be sharper and more grounded if you’ve at least tried to see what problem they’re actually solving.
Fourth, separate facts from feelings.
“This challenges my worldview” is not the same as “this is factually incorrect.”
When you feel your temperature rising, name it to yourself: “I don’t like this, but is it wrong? Or just uncomfortable?” That mental pause is where learning can sneak in.
Fifth, respond to the strongest version of the argument, not the weakest.
If there are obvious misphrasings, small mistakes, or easy targets, ignore them for a moment. Focus on the best, most reasonable interpretation of the other side’s point.
If you can defeat only the weakest version, you probably don’t understand the topic well enough yet.
The Real Flex: Being Calm, Curious, and Correct Over Time
We live in an era where shouting, dunking, and “destroying” people online is treated like a sport. It’s easy to get sucked into that. It feels powerful. It feeds the ego.
But in actual careers, where promotions, trust, and responsibility are on the line, the real flex is much quieter:
You read carefully.
You listen more than you speak.
You can handle being challenged without exploding.
You can change your mind in public without falling apart.
You write in a way that makes other people smarter, not smaller.
If you’re the person who always reacts emotionally, always misreads, always argues against points nobody made, and always walks away feeling “pissed off at people who don’t get it,” you might think you’re surrounded by fools.
But there’s another possibility: you’re broadcasting, loudly and repeatedly, that you’re not yet ready for bigger responsibilities.
The good news? This is fixable.
You don’t have to become a different person overnight. You can start with one simple commitment:
“For the next month, I will read to understand before I read to react.”
Do that in design reviews. In Slack. On LinkedIn. In email. In performance feedback.
Notice when your ego jumps in. Notice when you’re writing for your own satisfaction rather than for clarity. Notice when you’re more interested in talking people out of their facts than in learning something new.
And then, slowly, deliberately, choose curiosity over reflex.
Because at the end of the day, the people who reach and sustain senior, principal, and leadership roles are not the ones who shout the loudest. They’re the ones who can absorb complex information, handle disagreement like adults, and respond in ways that make the work and everyone around them better.
You can be one of those people.
But only if you’re willing to start with the boring, unglamorous, absolutely critical skill:
Read. Properly. Then write like it matters.
Take this advice, and your career will greatly benefit.
Looking forward to seeing you in the next article!
Leonardo Furtado