‘He was sincere and he apologised, I accepted it’ — Ger Brennan reveals Jarlath Burns’ phone call to say sorry for ‘irrational’ comment - Irish Independent

In the high-stakes world of elite sport, a public spat between a former player and a sitting GAA president would normally be resigned to the back pages. But when Dublin football legend Ger Brennan shared the details of a phone call with GAA president Jarlath Burns, the story transcended sport. It became a masterclass in conflict resolution - one that every engineering manager, tech lead, and open-source maintainer should study.

A phone call that resolved a public feud holds a lesson every CTO needs to hear. The exchange, captured in the headline 'He was sincere and he apologised, I accepted it' - Ger Brennan reveals Jarlath Burns' phone call to say sorry for 'irrational' comment, is more than a sporting anecdote. It's a case study in what happens when ego, stress, and miscommunication collide - and how a sincere apology can reset the relationship entirely.

In the software world, we spend an inordinate amount of time optimising code, APIs. And infrastructure. We invest in CI/CD pipelines, observability, and postmortems. Yet we often neglect the single most fragile dependency: human communication.

The Incident That Captured Ireland's Attention (and Why Engineers Should Care)

The original dispute erupted after Burns, in a moment of frustration, described a suspension decision as "irrational". Brennan, the recipient of that suspension, was understandably aggrieved. The comment went public - as everything does in the age of 24/7 sports journalism - and threatened to fester into a long-running feud.

Instead, Burns picked up the phone. Brennan later told reporters: "He was sincere and he apologised, I accepted it, and we move on, and " The full account in the Irish Independent paints a picture of two grown men choosing resolution over rancour.

Why should a developer care? Because the exact same dynamic plays out daily in Slack channels, pull request comments. And stand-up meetings. A lead engineer makes a dismissive remark about a junior's approach. A product manager labels a feature request "irrational". A CTO publicly disagrees with an architecture decision. Without a sincere follow-up, those micro-conflicts calcify into resentment that kills velocity.

Why Sincere Apologies Matter More Than Rational explanation

In engineering, we default to logic. When we offend someone, our first instinct is to explain why we were right - and why the other person misinterpreted us. We write long comments justifying our intent, and we point to evidence, data, or precedent

That's exactly the wrong approach. Brennan's key observation was that Burns was sincere. He didn't say, "You misunderstood my comment" or "The context was complicated". He simply apologised.

A Harvard Business Review study on workplace apologies found that sincerity - not elaboration - is the strongest predictor of forgiveness. In software teams, this translates directly to faster recovery after code review blowups or project postmortems.

The Psychology of 'Irrational' Comments in High-Stakes Environments

Burns' original comment was labelled "irrational" not by him, but by the media - and arguably by his own later admission. The word captures something every engineer recognises: the heat-of-the-moment outburst that doesn't reflect your actual beliefs.

In tech, irrational comments often emerge during:

• Late-night deploys when stress and caffeine collide.
• Code review marathons before a release deadline,
• Architecture discussions where strong opinions clash
• Postmortems where blame culture still lingers.

When a colleague says something hurtful, the rational part of our brain knows they were under pressure. But the emotional brain doesn't care. It registers the insult and holds a grudge. Brennan's willingness to accept the apology - "I accepted it" - is the second half of the equation. He didn't demand a formal hearing or a written retraction.

Ger Brennan's Conflict Resolution Model: A Playbook for Engineering Managers

Let's break down the steps Brennan and Burns implicitly followed. This is a pattern you can encode into your team's conflict escalation protocol:

1. Private outreach: Burns called Brennan. He didn't tweet a public apology or issue a press release, and he picked up the phone
2. Sincere acknowledgment: No hedging, no "if you felt". Just a Clear admission that the comment was wrong.
3. Acceptance and closure: Brennan used the word "accepted". Which signals he chose to move on. He didn't demand ongoing contrition.
4. Public unity: Both men went on record with the same story. No shadow narratives.

Compare this to how many engineering teams handle a toxic pull request comment: they escalate to HR, create a paper trail, and then avoid each other in meetings. The productivity cost of unresolved conflict is well-documented. Atlassian's blameless postmortem guide emphasises that psychological safety - the ability to admit mistakes without retribution - is the foundation of high-performing teams.

How Software Teams Can add 'Apology Culture' Safely

There's a fine line between fostering an apology culture and creating an environment where people feel obligated to apologise for everything. The key is to distinguish between mistakes in judgment (which deserve sincere apology) technical disagreements (which should be resolved through evidence and debate).

Brennan's example shows that the apology was about the tone and impact, not the underlying decision. Burns didn't say the suspension was wrong; he said his description of it as "irrational" was wrong. That's a critical nuance for engineering leaders.

• Apologise for how you delivered the feedback, not for having the feedback.
• Keep it brief: "I was harsh in that comment. I'm sorry. " - then move to the technical substance.
• Encourage team members to accept apologies gracefully. "I accept that, and let's fix the bug"

The Role of Public vs. Private Apologies in Open Source

Open-source communities are particularly prone to public flare-ups. Linus Torvalds' infamous 2018 apology is a textbook example. And in a public email to the Linux kernel mailing list, Torvalds admitted his confrontational style was hurting the community. He took a break and changed his behaviour.

Burns' approach was different - and arguably more effective, and he reached out privately firstOnly after the apology was accepted did the story become public (via Brennan's interview). The sequence matters: private sincerity builds trust; public apologies can sometimes feel performative.

In open source, a maintainer who publicly insults a contributor should follow the Burns playbook: DM the person - apologise sincerely, then optionally share that the issue has been resolved. Let the recipient control the narrative.

Measuring the Impact of a Leader's Apology on Team Productivity

What's the ROI of a sincere phone call? While hard to quantify, studies in organisational psychology provide clues. A 2020 meta-analysis published in the Journal of Applied Psychology found that leader apology significantly increases trust repair, especially when the apology is perceived as sincere (as Brennan emphasised).

In practical terms, a restored relationship means:

• Faster code reviews (no passive-aggressive nitpicking).
• Better knowledge sharing (grudges inhibit asking for help).
• Lower turnover risk (unresolved conflict is a top reason engineers leave).

Brennan's public statement - "We move on" - signals that the team can now focus on the mission: winning matches. For a tech team, the mission is shipping great software. Every unresolved conflict is a drag on that mission.

Practical Steps for Tech Leaders: From 'I'm Sorry' to 'We Move On'

You don't need to be a GAA president or a Dublin footballer to apply these lessons. Here are concrete actions you can take this week:

1. Scan your Slack history for any comment you made that could be interpreted as dismissive. Reach out privately to the recipient.
2. Model the behaviour in your next one-on-one: if a report raises a conflict, validate their feelings before jumping to solutions.
3. Create a "phone call" policy for serious disagreements. No escalating via email or Slack,? And pick up the phone, as Burns did
4. Audit your postmortem process - does it encourage blame-free confession? Or does it pressure people to rationalise their mistakes?

Remember: the goal is not to eliminate conflict. The goal is to resolve it quickly and sincerely. So the team can move on.

Frequently Asked Questions

1. How does Ger Brennan's apology acceptance apply to remote-first engineering teams? Remote work lacks non-verbal cues, making sincerity harder to convey. A video call - even a phone call - is far more effective than a Slack message. Brennan's story underscores the importance of voice contact in conflict resolution.
2. What if the apologiser isn't sincere Brennan explicitly stated Burns was sincere. If you suspect insincerity, address it directly: "I appreciate the apology. But I need to know you understand why it hurt. " That can prompt a deeper conversation.
3. Should I apologise for a technical decision that was correct but upset someone? Yes, but separate the content from the delivery. "I still believe the Rust refactor is the right call. But I am sorry for making you feel your C++ experience was dismissed. That wasn't my intent. "
4. How do you teach junior engineers to give sincere apologies? Pair them with senior engineers during code review. Show them how to say "I was wrong" without it feeling like a career risk. Blameless postmortem culture is a great training ground,
5. Is there a risk of over-apologising Yes. Constant apologies for minor issues can erode confidence. The key is proportionality. And use the "phone call threshold" - if the issue warrants a direct conversation, it warrants a sincere apology if needed.

What do you think?

Have you ever experienced a workplace conflict that was resolved by a sincere apology from a leader? What made it effective or ineffective?

In open-source communities, should apologies be handled privately or publicly? Does the Burns approach scale beyond two-person interactions?

How would you design a "conflict resolution protocol" for your engineering team that encodes the steps both men followed - private outreach, sincere acknowledgment, acceptance,? And moving on?

Conclusion: Ger Brennan's revelation about Jarlath Burns' phone call isn't just a sporting footnote it's proof that public conflict can be defused with a simple, sincere apology - if both parties are willing to prioritise the relationship over being right. As engineering leaders, we have a choice: let grudges compound like technical debt. Or call a timeout, say sorry. And get back to building. The Irish Independent headline captured it perfectly: 'He was sincere and he apologised, I accepted it' - Ger Brennan reveals Jarlath Burns' phone call to say sorry for 'irrational' comment. Now it's your turn to make that call.

If this resonated, share it with a teammate you've been avoiding a conversation with. Then pick up the phone.