Mac Chaffee interviews ngrok infra team about technical disagreements
Engineer reflects on workplace conflicts by studying how peer team handles similar technical disputes.
Conversation activity · last 3 days peak 3/hr
Summary, timeline and people extracted by Claude from 21 items across 1 source · 22h ago. Quotes are verbatim.
Mac Chaffee, a DevOps engineer, wrote a sponsored post about interviewing the infrastructure team at ngrok to understand how other teams handle technical disagreements—a recurring source of friction in his own career. The piece, which generated discussion on Lobsters, explores whether technical disputes are worth the interpersonal cost and examines the author's journey from conflicted early-career engineer to someone seeking perspective on how to work better with colleagues.
- Engineer interviews peer team to gain perspective on recurring workplace conflicts rooted in abstract technical disagreements.
- Lobsters community debate centers on whether technical disagreements materially affect company outcomes, with positions ranging from 'most don't matter' to 'bad decisions can tank companies.'
- Author's broader concern: whether technical conflicts are worth damaging professional relationships and personal well-being.
- Post resonates strongly with readers; many report similar experiences with workplace conflicts and damaged friendships over technical choices.
How it unfolded
-
Reaction Appreciation for cited sources
fbegyn notes the value of Chaffee's references to source material and indicates they are ordering recommended books.
-
Reaction Debate over decision impact
Commenters epidemian and icefox share experiences of technical decisions with real consequences, while discussing the author's themes of personal relationships damaged by disagreements.
-
Reaction Positive reception and engagement
Multiple commenters praise the post's relevance and depth, with bitshift and jmtd expressing appreciation for the reflective quality of the piece.
-
Reaction Discussion on technical stakes emerges
Commenter mplant argues that most technical disagreements don't matter to company success, while others counter that bad decisions can tank companies.
-
Report Blog post published on Lobsters
Chaffee's sponsored post "Am I the problem? Interviewing another team to find out" is posted to Lobsters, discussing his past conflicts at Cisco and what he learned from interviewing ngrok's infra team about workplace disagreements.
- 18 weeks quiet
-
Event Chaffee interviews ngrok infra team
Chaffee conducted interviews with ngrok's four-person infrastructure team, including James, Stacks, Alex, and Sabrina, gathering thirteen pages of notes on how they approach technical decisions and conflicts.
What people are saying verbatim
“I'd like to thank ngrok for supporting my "art" (weird ranty tech blog posts). They paid me to write this post, but the opinions and stories here are my own.”
Mac Chaffee · macchaffee.com blog post
“I feel like there are so many abstract hills to die on. But maybe that's just me? Or just the teams I'm on?”
Mac Chaffee · macchaffee.com blog post
“I think something that really helped with this was realizing that fundamentally it did not really matter if I won an argument, especially in a workplace.”
mplant, Lobsters commenter · Lobsters
“I've worked on companies where bad technical decisions negatively affected products, sometimes even completely tanking them, and ending in the eventual downfall of the company.”
epidemian, Lobsters commenter · Lobsters
“I'm not sure what I was expecting when I opened this but it was far richer and more profoundly relevant to me than I realised.”
jmtd, Lobsters commenter · Lobsters
“The fact is 99.9999% of technical disagreements have absolutely no effect on the success of a company, and if your opinion mattered that much to effect things so dramatically you'd be in a position where you could just tell people what to do”
mplant, Lobsters commenter · Lobsters
Voices from the web unedited
-
If you’re on the hook for overnight support of a system you might feel differently.
-
I think something that really helped with this was realizing that fundamentally it did not really matter if I won an argument, especially in a workplace. Because really I was just giving my opinion, and it's not like I was smarter than anyone else. There is no technical disagreement in basically any context that if were to "lose" that would result…
-
I’m not sure what I was expecting when I opened this but it was far richer and more profoundly relevant to me than I realised. Thanks for sharing
-
Hmm, that doesn't really match what i've seen in this industry. I've worked on companies where bad technical decisions negatively affected products, sometimes even completely tanking them, and ending in the eventual downfall of the company. These were small-ish startups, yes. And there were other factors that contributed to the failure of the…
-
> This was my first job out of college, so I had all the energy and wisdom of a sledgehammer. Got me smiling right at the start.
-
> Remember that friend from Cisco I stopped talking to? I had been thinking about messaging her again for like a solid year, but I really struggled to overcome the shame of getting into all those pointless arguments and ruining a friendship as a result. Would she be holding a grudge of her own? Would she even see my message? I recently went…
-
> Because really I was just giving my opinion, and it's not like I was smarter than anyone else. I think even in your proposed situation, "losing" an argument doesn't _actually_ mean that your being on the hook for overnight support of a system is a problem, or should make you feel differently about the stakes for that argument. Mostly because you…
-
The fact is 99.9999% of technical disagreements have absolutely no effect on the success of a company, and if your opinion mattered that much to effect things so dramatically you'd be in a position where you could just tell people what to do
-
I've had a mixture for sure: times when my life would get worse if I lost, and times when it felt that way but I was just over-reacting or already burnt out, or other kinds of team dysfunction like poor ownership. Tech work can be a double-edged sword: we often get a lot more power to choose what we work on than other kinds of workers, but we also…
-
I have a thought that I hope doesn't come across too rejective or something. But I have a feeling that present day management and company structures - also outside of our industry - are extremely flawed. I think that wrong ideas have been picked up at spread. Productivity should be high, everyone is burned out but nobody has actual solutions but…