Fight for the Future

Every engineer has the same fear. It's not that their code will break in production — they can handle that. The fear is that someone will look at what they built and silently conclude they're an idiot. That the architecture review is actually a competence trial. That the post-mortem is a sentencing hearing.

This fear runs everything. It's why teams default to two modes: conflict avoidance or combative posturing. Either nobody says the hard thing, or someone says it like a blade. Consensus theater or gladiatorial code review. Both are defense mechanisms against the same imagined judgment, and both produce the same result: the actual problem doesn't get addressed.

I do something different, and it took me a long time to realize it was unusual.

The Gate That Isn't a Gate Anymore

I was trying to explain this to my wife recently, and I reached for an analogy from art. In any art form, there's the representation of the thing — the painting, the symbol, the model — and then there's the actual thing being represented. These are not the same. The picture of an apple is not an apple.

Engineering systems work the same way. There's the system as it was designed, built, and ran — and then there's the actual problems the system alleviates, which exist in an evolving environment while the system stayed still. The architecture diagram on the wiki is a representation. The production environment at 3am is the territory.

When I walk into a room to advocate for change, I'm not attacking the representation. I'm not saying "this system is bad" or "whoever designed this didn't think it through." I'm pointing at the gap between the representation and the current reality. The gate your team built was built to spec. Everyone signed off on it. It worked for years. I say because the terrain changed, and the gate doesn't match the terrain anymore, we don't need to defend the gate. We need to go look at the actual ground.

This reframe changes everything about how a room responds.

Why It Works

Engineers who built the current system did it under constraints nobody else saw. They had deadlines that got moved. They had dependencies that shipped late. They built something that worked despite the limitations. That's not incompetence — that's engineering.

I know this because I'm that engineer too. I've written the code that I'd be embarrassed to explain. I've made the architectural decision that seemed right with the information I had and looks indefensible eighteen months later. Everyone has. The gap between "what I built" and "what I'd build now" is not a character flaw. It's just time passing.

You can be relentless about a problem without making anyone defensive. You're not asking them to admit they were wrong. You're asking them to look at where we need to go. The current state is not on trial. The desired state is the only goal in the room.

What People Haven't Seen

The reason this lands so hard when it works is that most people have never seen it done. They've seen people who avoid conflict until the system is on fire. They've seen the senior engineer who walks in and dismantles someone's design in front of their peers. They've seen the architect who's technically right and personally devastating.

They haven't seen many people be genuinely relentless about a problem — keep pushing, keep insisting, keep refusing to let the room settle for a comfortable non-answer — while never once making it about the people who built what's there. It shifts something in the room. People realize they can engage with the problem without risking their standing. The defensiveness drops. The actual engineering starts.

This isn't a soft skill. It's not "being nice." I'm not nice about it. I'm persistent and direct and I will not let a room full of smart people talk themselves into doing nothing because doing nothing feels safe. But I'm fighting the problem, not the person, and people can feel the difference immediately.

The Hardest Part

The hardest part isn't doing it. The hardest part is wanting to do it again.

Every time I see a system that needs to change and a room full of people who've built their identity around the current state, part of me just wants to write the blog post instead of having the conversation. It's exhausting to be the one who points at the terrain. It would be easier to let the gate stand and route around it.

But the problems are real, and they don't fix themselves, and the people in the room are capable of extraordinary work if someone can get them past the fear that engagement means judgment. Help others focus on the problems of today.