The architect in the room.

I am Manuel Vázquez. I am an architect.

Not a developer — though I can write the code when I have to. The distinction matters. A developer builds what you ask for. An architect figures out why what you asked for will fail in three years, and builds something better instead.

I have been doing this for 30 years. In that time I have built systems that are still running. Healthcare infrastructure. Billing platforms. Enterprise cloud migrations. The specific technologies I built on — open source stacks, Linux, Proxmox, open standards — are still here. Many of the frameworks people were chasing when I chose not to chase them are not. This is not coincidence. It is what happens when you build for the decade, not the demo.

What I actually do is difficult to explain with a job title. I walk into an organization and I see the specific places where the next five years of growth will cause the architecture to break. I see the debt accumulating in corners of the system that nobody is watching. I see the integration that looks solid but has a single point of failure that hasn't cost anyone yet. And then I fix it — before it takes a quarter of the budget and six months of someone's year.

I am also, when the situation calls for it, the person who tells the room what it does not want to hear.