This one is on me… mostly. If you see yourself in it, that’s on you too.

Years of wins, mistakes, and “we should’ve seen that coming” moments, shared so you can skip a few bruises.

As my career went on and I collected enough scars and bruises, I mostly shared my lessons in the wild: during coffee breaks with the team, in hallways, in 1:1s, in the office, in airport terminals, and in those “why are we still awake?” Slack threads.

Now that I post more often and not just in private channels, I get a few well-meaning questions:

“Everything okay over there? That post felt… targeted.”

Let me clear that up. Something recent can spark a thought, yes. But when I write about leadership, engineering culture, or teams under pressure, I am pulling from the entire mosaic of the good, the bad, the confusing, and the “please let future me find this funny” moments that piled up across my career.

I’ve worked across different countries and cultures. I’ve led teams in environments built on clarity and others powered by duct tape and improvisation. I’ve volunteered in community groups and jumped into ad-hoc teams during full-blown chaos. I’ve worked in places with clear processes and places where “process” meant one person who remembered everything. I’ve been in teams where engineers happily passed the keyboard, and teams where two people sitting three feet apart emailed each other instead of speaking (I kid you not). I’ve worked under leaders who gave context and leaders who gave surprises, and that phase permanently cured me of any love for surprises.

I hate surprises. (I love wonders, though.)

I’ve seen orgs where decisions lived in documentation, and orgs where knowledge survived as oral tradition and decisions were treated as folklore passed down by senior engineers. Their words, not mine.

But everywhere I went, I saw the same thing: people trying to build something meaningful while navigating each other’s quirks, fears, strengths, and blind spots.

Patterns repeat. Geography doesn’t change them. Industry doesn’t either.

You might assume that when I describe a leader dodging a decision, a team sitting on unspoken frustration, or a cross-functional group looping on the same disagreement for weeks, I must be talking about something that happened yesterday.

I’m not.

I’m pulling from a long archive of moments that stack up the longer you work with humans:

• the sprint where the timeline made sense only if physics stopped applying and everyone suddenly gained superpowers

• the meeting where everyone agreed, mostly because no one wanted to reopen the argument

• the project that “absolutely had support”… until it didn’t, when it started and the first obstacle appeared

• the decision that somehow changed three times on its way from leadership to the team

• the tension between two groups who needed each other but shared zero incentives, which is a fun way to create tension without needing a villain

• the incident review where the real root cause was “we avoided this conversation for six months”

These moments aren’t tied to one company. They’re tied to the human condition inside organizations.

So when you recognize something in my writing, it doesn’t mean I’m talking about your team. It means your team is not the first to run into it, and neither was mine.

Raw files, not filters

You might expect leadership posts to read like a polished keynote: clean arc, clear lesson, neat bow on top. Real work doesn’t look like that, so my writing doesn’t either.

I write in raw files. The moments as they happened, not as they would appear in a slide deck:

• the 1:1 where someone finally said “I can’t hold this alone anymore”

• the status meeting where everyone avoided saying the deadline was already gone

• the sprint where the plan doubled while the team shrank

• the quiet standoff between two groups who needed each other but shared exactly zero incentives

• the reorg that solved one problem and created three fresh ones before lunch

• the late-night Slack ping that started with “quick question” and ended in a mini-postmortem

• the retro where someone finally said the sentence everyone else had been thinking for weeks

These aren’t stories crafted for effect. They’re frames pulled straight from real rooms, real teams, and real messiness.

You can edit them however you want, sharpen the contrast, crop the edges, or adjust the lighting. My version isn’t the definitive version, it’s just the unfiltered one.

My mistakes are part of the story, not footnotes

If I’m going to show the raw files, mine have to be included too. Leadership gives you plenty of material, and not all of it is flattering.

I’ve let people down: my leaders, my team members, myself. I’ve misread situations and I jumped in too fast or waited too long. I burned my self out and I burned my team mate out. I’ve watched projects crack under pressure and knew part of that pressure came from me.

Here are the unedited versions:

• I redirected a project long after everyone already knew it needed a reset.

• I kept someone in a role that no longer fit because the alternative required a harder conversation.

• I leaned too much on high performers because they were reliable, and yes, they noticed… and one even burned out.

• I stayed quiet in meetings when the team needed clarity, not my silence.

• I approved a plan that should have been sent back to the desk.

• I escalated an issue before giving the team a chance to recover on their own.

• I let stress into my tone and watched the energy in the room drop immediately.

But the other side is real too:

• I’ve also coached people into roles they didn’t think they could handle.

• I’ve pushed for promotions that took months and political patience.

• I’ve shielded teams from unnecessary pressure so they could focus on doing the work.

• I’ve fought for people when it wasn’t convenient.

• I’ve rebuilt messy systems with people who were tired but committed.

• I’ve been challenged, corrected, supported, and lifted by engineers, PMs, designers, and operators who wanted the work — and me — to get better.

Leadership is not a tidy sequence of victories. It’s a long list of decisions, conversations, regrets, repairs, and the occasional win that reminds you why you care.

Anyone who leads long enough collects both sides. The only difference is whether you pretend otherwise.

If you recognize yourself, good

If you recognize yourself in something I write, that means you’re paying attention. These situations repeat across roles, companies, and levels, and nobody is immune to them.

And if a line stings, take a moment to look at why. We all flinch when we see a habit we’ve been avoiding or a version of ourselves we’ve outgrown. I do it too. There are paragraphs I write that make me wince, because I remember the exact moment I learned that lesson the hard way.

I’m not speaking from a distance, I’m in the same mirror as everyone else, describing patterns I’ve lived through and sometimes contributed to.

Seeing yourself in these moments isn’t a problem. It’s a sign you’ve hit the point where awareness can turn into action.

Patterns repeat — everywhere

Every company believes its challenges are unique. They are unique in flavor, but the ingredients are surprisingly familiar.

I’ve seen leaders avoid a hard conversation until the small issue became the project’s biggest risk. I’ve watched dependable engineers quietly carry emotional and technical weight while everyone assumed they were fine… Until one day they snapped and handed notice.

I’ve sat in meetings where two teams used the same words but described completely different realities. I’ve seen PMs trying to translate strategy that wasn’t fully formed. I’ve watched designers argue for quality while deadlines ate their arguments for breakfast. I’ve seen Ops turn into the unofficial glue that holds everything together without having the authority to match the responsibility.

I’ve watched cross-functional groups go in circles because their incentives never aligned in the first place. I’ve seen reorgs launched before anyone could clearly state the actual problem they were supposed to solve.

None of this belongs to one company or one era. It’s what organizations do when humans work together under deadlines, ambiguity, and pressure.

These patterns aren’t personal, they’re predictable.

Once you see them, you start noticing them everywhere: not to judge, but to understand what you’re dealing with.

Why clarify this now?

I didn’t start noticing these patterns yesterday. I’ve seen them for years: in teams I led, teams I joined, teams I supported, and teams I accidentally made harder for. The only difference now is that I came back to something I’ve always enjoyed: writing and sharing what I’ve learned along the way.

I’m writing again because the moment calls for it. We’re in a strange mix of challenging and exciting times. Engineers who once looked untouchable on the market are now on layoff lists. Teams are smaller, but expectations are not. The pressure didn’t disappear; it simply shifted onto fewer people.

When the landscape shifts this quickly, good leadership stops being optional. It becomes infrastructure.

If something I share helps you avoid one painful lesson or support your team with a steadier hand, the writing is worth it. Nobody needs to learn everything the hard way. I certainly didn’t. Much of what I know came from people who shared their mistakes and their wins with me.

So I’m doing the same now. Not to sound alarms, but to offer something useful in a moment when clarity is in short supply.

These lessons come from everywhere: my own experience, books, mentors, teammates, and the conversations that start only after the meeting ends and people finally say what they actually think.

And here’s one thing I’ve learned the slow way: with people, prevention costs far less than mitigation. That rule doesn’t always hold for code and bugs, though.

---

All these moments shape how I think, how I write, and how I lead.

I’m a mosaic of those experiences, and so are you.

If something in my writing feels familiar, good. Familiar means you’re spotting a pattern. And once you can see a pattern, you can change it if you want to.