The engagement started with a decommission notice on a system nobody had fully mapped.
The system processed a significant chunk of daily financial data. A risk management platform, wired deep into a legacy mainframe that was still very much alive, and very much a black box. Outside that mainframe sat a single overbloated component doing the work of several, holding the integration layer together through years of accumulated dependencies nobody had ever fully mapped.
There are meetings where everyone in the room knows the truth and nobody says it.
I’d been through the existing codebase. The designs were rough; the code behind them was worse, not catastrophically wrong, just badly built, in the way that happens when a team has been too busy to be honest with itself, and too stubborn to revisit the amateur choices it had made along the way.
I’d written it up. They’d seen my assessment and recommendations, but a new deck was better.
The meeting opened with a presentation: architecture diagrams, process flows, the kind of thing that takes real effort.
I didn’t say much.
The manager called me in.
I already knew.
I’d known for weeks, in the way you know something before you’re willing to say it out loud.
The conversation was ten minutes.
The decision had already been made, by both of us, long before that.
Quality is subjective.
Architecture is judgemental.
So how on earth do we measure it?
Every architecture review, every design workshop, every committee meeting eventually hits the same wall. Someone asks: “But is this actually good?”
We pretend the answer lives in metrics. Response times. Availability. Coupling scores. Maturity models. Dashboards filled with comforting colours. We convince ourselves that if the numbers are green, the architecture is good.
That is the uncomfortable reality: half the time, those numbers are illusions. They tell part of the story.
I’ve witnessed perfectly green dashboards collapse the moment real business pressure appeared.
Show me an architecture no one questions,
and I’ll show you a system no one understands.
A few years back, I walked into a post-mortem where the architecture was being blamed for everything from latency spikes to the office coffee machine malfunctioning.
The architect? Well, he was calm. Unbothered. Certain.
“It’s not the design,” he said.
“The team just didn’t implement it properly.”
There it was: the dead giveaway. He wasn’t doubting the design. He was defending it like gospel.
Right then, I knew.
The most dangerous architect isn’t the one who lacks answers.
It’s the one who never asks questions.
If you’re an architect or becoming one, doubt isn’t your enemy.
It’s your sharpest tool.
errorless (adj)
Free from error, accurate, correct. Being complete of its kind and without defect or blemish.
Walk through enough architecture reviews and you start recognising a specific shape of failure. The system isn’t wrong. It’s too right. Every edge case has a handler. Every failure has a fallback. Every component is wrapped, secured, and isolated from everything else. The development cost is enormous. The operational cost is worse. And when the requirement changes, which it always does, nothing moves.