So I finally started a blog.
I’ve been meaning to do this for a while. I spend a good chunk of my time thinking about software architecture, engineering leadership, and the day-to-day realities of building systems that actually hold up — and somewhere along the way I figured I should start writing it down.
Who I am
I’m a software engineer based in Florianópolis, Brazil. I’ve been doing this for about 5 years — mostly in the .NET and cloud space (Azure and AWS). I’ve worked across the stack from monoliths to microservices, and right now I’m a Technical Lead at AB InBev, where I lead a senior team working on global operations.
My day-to-day involves a lot of system design decisions, stakeholder coordination, and trying to close the gap between “the architecture on the whiteboard” and “the thing running in production.”
What I’ll write about
Mostly things I run into at work and think are worth documenting:
- .NET and C# — patterns, gotchas, architecture decisions
- Cloud — Azure and AWS in practice, not just theory
- Engineering leadership — what actually happens when you’re tech lead
- System design — how to think about it, not just memorize it
- Database performance — because bad queries always come back to haunt you
I’ll keep it practical. I’m not interested in writing content for the sake of it — I want to write things I’d actually want to read.
Why now
I recently went through a big migration project at work — ripping out a legacy system and redesigning the architecture from scratch with a tight deadline and a multilingual team. There was a lot to learn and I didn’t document enough of it while it was happening. I don’t want that to keep being the pattern.
Writing is how I think. This is where that thinking lives now.
If something here is useful to you, great. If you want to talk about it, find me on GitHub or LinkedIn.