Who I am and why I write in Spanish

I started in IT without knowing English well. I had to learn both at the same time: how to program and how to read documentation that was almost entirely in another language. That double barrier slowed me down, not because I lacked ability, but because the resources weren't there in Spanish the way they needed to be.

I'm a Software Engineer with 9 years building distributed systems across Caracas, Santiago, and Barcelona. My foundation is the Java ecosystem: Spring Boot, Spring Modulith, Hibernate, Maven. Over the years I added Kotlin, picked up gRPC before it was mainstream in the JVM world, and went deep into event-driven design with Kafka. I've worked with relational databases under real load, built services on top of AWS and DigitalOcean, and operated systems on Kubernetes in production.

More recently I've been working with Temporal for workflow orchestration, exploring agentic architectures with RAG and GitHub Actions pipelines, and thinking seriously about how AI changes the way we build backend systems. Not as a trend to follow, but as a genuine shift in what's possible with a small team.

Alongside engineering I'm building Waraflow, a product for property cleaning management. That means I'm also a founder, which means I deal with the gap between what architecture books say and what you actually ship with limited time and a small team.

Why Spanish

There's no shortage of technical content in English. There is a shortage in Spanish, specifically content that goes beyond translating documentation and actually shares what it's like to make architecture decisions, debug distributed failures, and build products from Latin America or Spain.

I don't want to write theory. I want to write about the real decisions: why we chose Kafka over RabbitMQ in a specific context, what broke in production and why, what I'd do differently if I started that service today. That kind of content exists in English across dozens of engineering blogs. In Spanish, much less so.

What you'll find here

Three tracks:

• Architecture — distributed systems, event-driven design, Java and the JVM ecosystem. Real implementations, not diagrams.
• Devlog — building Waraflow in public. The decisions, the mistakes, the tradeoffs of a real startup.
• Tools — things I use every week and actually recommend. Short and direct.

You don't need perfect answers to write. You need to share what you actually lived through. That's what I'm doing here.