Loading today’s stories
Build1 distinct publisher3 min readPublished
Sean Goedecke argues that visible anger gets you excluded from the conversations where the interesting work is handed out, and the awkward part is that his own essay rates those engineers above average at shipping, so no dashboard catches the loss.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
Routing around damage is the right metaphor, and it is worth being literal about the packets. Nobody convenes a meeting to cut you out. One person decides not to raise a design question in the channel you read, another walks a decision into a DM, and what Goedecke describes is the sum: exclusion from conversations that might set you off, plus decision-making done in backchannels [5]. Each individual choice is cheap and defensible. The aggregate is that a class of work stops passing through you.
That is why the failure does not show up where people look for it. He rates angry engineers well above average at solving tickets and shipping features, whatever their cultural cost [11], and the routing removes them from conversations rather than from queues [5]. Throughput holds while the scope of what reaches the queue narrows, which makes a sprint board the wrong instrument for detecting any of this [18].
There is a seam in the argument worth naming. Goedecke also holds that effective engineers get listened to, at minimum by colleagues and eventually by managers and product managers who want to extract value from them [8]. Set that beside the above-average output claim and it reads like a contradiction, until you notice how he defines effectiveness: every successful project involves other people, so if nobody listens to you, you cannot run one [9]. That definition carries the whole essay [19]. It also means the familiar complaint about holding the company together while nobody listens, which he says is almost never true [7], can be false about influence and roughly right about output at the same time.
The line I would hand to anyone who thinks the diagnosis is about other people is his own best case: a tight-knit team of confident colleagues who are not put off, which stops holding the moment someone less confident joins or you have to communicate outside the team [4]. That is a claim about blast radius, not about temperament. Blast radius is the thing that grows as you get more senior.
Where I would push is the fix. The model is a vertical tube, open at both ends, filled with emotional investment pumped in from below: too little drains away and you coast, too much overflows and you become someone people work around [15]. Remedy one is to care the exact right amount, with hobbies and family for perspective, on the grounds that a rich personal life makes it hard to end up yelling at somebody about React state management [16]. He concedes that balance is tricky to hold over time [16]. Remedy two is to care about different things, since overflow comes from caring about what the organisation does not, and tight alignment (his example is caring primarily about delivering shareholder value) lets you fit far more investment in [17].
In my context the second is the one that survives a bad quarter, and the useful version of it is narrow. For me it has meant working out which of the things I care about the organisation will never pay for, and keeping the investment out of that end of the tube.
Ranked by verification strength, evidence, and original report placement.
Goedecke argues an angry colleague immediately becomes a new problem to be managed rather than a professional helping you manage problems.
When someone is visibly angry in a meeting or in Slack it kills the atmosphere, and other engineers often go quiet entirely rather than risk making the situation worse.
Goedecke says the best case for routinely getting heated is a tight-knit team of confident people who are not put off by it, and that it becomes a big problem the moment a less confident person joins the team or you have to communicate outside it.
Healthy workplaces route around anger the way networks route around damage: emotionally unreliable engineers get left out of conversations that might cause them to blow up, and decision-making gets done around them in backchannels.
Goedecke has seen this become a self-reinforcing cycle: angry engineers are not consulted on key decisions, which makes them angrier, which pushes them further from the spaces where decisions get made.
One reason effective engineers get listened to, per Goedecke, is that all successful projects involve working with other people, so if nobody listens to you, you cannot do that.
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 29, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
build
Do Not Reboot The Box: A Five-Minute Triage Order That Survives A 3 AM Page1 distinct publisher
build
With CRA out of React's docs, the new project default is a rendering decision1 distinct publisher
invest
Salesforce's double digits, minus Informatica: agentic AI is real and still 2% of revenue1 distinct publisher
build
A build-tool swap that took 70 days and 166 files, and the build was the easy part1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One career, no counts
The load-carrying empirical statements — that angry engineers out-ship the average, that caring alone is enough to make someone competent, that the 'nobody listens to me' complaint is almost never true — are all backed by the phrase 'in my experience' and nothing else. Goedecke is transparent about that, and about having been the angry engineer himself, which makes the piece honest testimony rather than measurement. Where he describes mechanism instead of magnitude, the account stands up on its own terms.
Nothing here to count
No release, no deployment, no survey, no policy anyone has put into practice — this is an argument about conduct, and the supplied reporting offers no trace of it being taken up. There is a neat irony: the harm Goedecke describes is invisible to the systems that record anything, so the story gives us nothing to measure for the same reason he says managers miss it.
Absolute rule, hedged argument
'You should never be angry at work' is presented as the one thing worth being prescriptive about, then walked back three times in the same piece: a little anger signals care, builds rapport, draws attention to what matters, and a fully professional robot has an uncanny-valley problem. The exclusion mechanism underneath is convincing; the universal rule wrapped around it is doing more work than the evidence lets it. Modest overstatement, not manufactured stakes.
Nothing being sold, one convenient cure
No employer, tool or product stands to gain: the essay is on the author's own site, and the only asset in play is his standing as someone whose advice is worth reading, reinforced by a link back to his earlier piece about his own worst day. Where interest does show through is the second remedy — realign what you care about with what the organisation cares about — advice that is considerably more comfortable for the organisation than for the engineer taking it.
Clear text, unanswered subjects
We have the piece in full and its argument is unambiguous, so describing what is being claimed carries little risk. Judging whether it is true is another matter: one observer, one flavour of employer, and the two groups whose behaviour is central — the engineers being routed around and the managers doing the routing — never get a turn.