Principal Software Engineer with 20+ years of experience building, breaking, fixing and occasionally understanding software systems.
I've worked across backend, frontend, cloud, architecture, consulting, product and engineering leadership.
These days, I'm mostly interested in software architecture, distributed systems, .NET, Go, AI, and the uncomfortable decisions that happen between "it works" and "we should probably run this in production".
> experience != knowing all the answers
> experience == having seen some of the wrong ones before
- 🏗️ Systems that can survive their own success
- 🧠 Architecture driven by problems, not diagrams
- 🧹 Keeping code easier to change than to explain
- 🤖 Using AI to remove boring work — not engineering judgment
- 👥 The inconvenient fact that software is mostly about people
- 🔥 Learning from production, the world's most honest reviewer
C# · .NET · Go · TypeScript · Azure · GCP · Docker · Kubernetes · GitHub Actions
...and whatever makes sense for the problem.
I don't collect technologies. I use them.
I still have a personal blog.
Yes, a blog.
In 2026.
I write about software engineering, architecture, programming, AI, technical leadership, mistakes, opinions that may age badly, and things I know I'll forget how to do in three years.
cuando en mi máquina tampoco funciona...
Code is temporary. Technical debt is surprisingly persistent.