There's a passage in Zhuangzi about a cook who carved oxen with such mastery that his blade never needed sharpening. He didn't cut — he found the natural spaces between tissues. The effort disappeared. Only the result remained. That is the standard I pursue in engineering.
The Paradox of Invisibility
In financial markets, the best sign that a system works perfectly isn't zero error occurrences in logs — it's the absence of conversations about the system. When a banking correspondent processes an FGTS withdrawal and approval arrives in seconds, they don't think "what amazing technology." They think "what fast service." That's the goal. The technology disappears. Only the result remains.
The Support Ticket as Architecture Metric
There's a metric few CTOs track: the proportion of support tickets that mention "the system" as the protagonist. When a user opens a ticket saying "the system crashed", you don't have a UX problem — you have an architecture problem. At Prata Digital, the goal was never to "reduce downtime". It was more ambitious: make downtime so distant a concept that it stopped making sense to monitor. Twelve months. Zero downtime.
The philosophy of invisibility
What is "mushin" applied to engineering?
Clique para ver a respostaThe state where technical mastery is so complete that effort disappears. The system works so well that nobody — not the team, not the user — thinks of it as a risk.
How do you truly measure architecture quality?
Clique para ver a respostaBy the proportion of support tickets that mention "the system" as the cause. The lower that number, the better the architecture. Zero system tickets = operational perfection.
Why do mediocre engineers prefer rewriting to refining?
Clique para ver a respostaBecause rewriting has visibility. Refining — making an existing system work better, silently — has no easy recognition. But that's exactly what defines real excellence.
What's the difference between availability as a goal vs. as a reality?
Clique para ver a respostaAs a goal, it's an anxiously monitored aspiration. As a reality, it's something the team stops monitoring nervously because they trust it's there. Reaching the second level is the real objective.
The Price of Invisibility
Nobody applauds what they can't see. Infrastructure that doesn't fail never makes headlines. The data pipeline that processes R$1 billion without failing even once is, paradoxically, the most invisible work that exists. That's why mediocre engineers always prefer rewriting to refining. A new platform has visibility. An existing system that simply works — better than ever — is too silent to impress those who don't know where to look.
The system must be reliable enough that the entire team stops thinking of it as a risk. When that happens, engineering has freed up mental space for innovation — not survival.
Excellence isn't visible because it's perfect. It's invisible because it's silent.
— Victor Fornitani