Senior software engineer based in Florianópolis, Brazil — ten years building scalable backend systems, distributed architectures and the teams behind them.
I started out building web systems and e-commerce platforms across projects of very different sizes. That's where I learned early that the hardest part is rarely writing code: it's creating alignment between people, processes and business rules so the software keeps evolving after the first release ships.
That lesson became the core of what I do today. I work with software engineering, distributed systems architecture and scalable platforms — architectural decisions, service integration, messaging, microservices and the evolution of legacy systems that have to stay standing while they change.
Across all of it, my priority is the same: reduce complexity and increase reliability. I favor metrics-driven decisions over opinions, and systems that are simple to operate over architectures that only look impressive on a diagram. Increasingly I use AI as a tool for that work, not as a replacement for engineering judgment.
That's exactly what I write about here — software architecture, code quality, performance, platform engineering and AI-assisted development — always drawn from real problems found while building and maintaining systems in production.
I hold a degree in Systems Analysis and Development, with a specialization in Software Architecture and Technical Leadership. That combination is what interests me: hands-on engineering alongside the work of growing people, processes and high-performing teams.
Articles on architecture, code quality and distributed systems.
How to keep services consistent without distributed transactions: compensating transactions, orchestration vs choreography, a practical PHP + RabbitMQ example and the most common pitfalls.
Read articleWhat Code Smells are, why Code Bloaters show up, and how to spot large classes, methods with too many responsibilities, duplicated code and Data Clumps.
Read article