After years of meaning to start one, here it is.
I’m João — a Senior Software Engineer on the Architecture & SRE team at Zwift, based in Rio de Janeiro. My day-to-day is a mix of platform reliability, incident response, observability, and the kind of slow, unglamorous work that keeps production from catching fire.
Why a blog?
The honest answer: I learn best by writing. There’s something about forcing an idea into sentences that reveals whether you actually understand it or were just pattern-matching on vibes. I’ve been keeping private notes and post-mortems for years — this is me making some of that public.
I’m also aware that most of what I know came from other people sharing their experiences online. This is me trying to give some of that back.
What I’ll write about
Mostly things I’m working through at work or studying on my own:
- SRE practices — SLOs, error budgets, toil reduction, on-call culture
- Reliability patterns — what actually works in distributed systems and what looks good in diagrams but falls apart at 2am
- Incident reviews — lessons from things that broke (with details changed as needed)
- Tooling & automation — the infra and scripts that make life better
- Career — growing from engineer to senior, and what I’m still figuring out
A bit of background
I’ve been building software professionally since 2017. I started at Radix as a backend engineer, spent a year at the Apple Developer Academy (and got to attend WWDC 2016 on an Apple scholarship), and have been at Zwift since 2019 — moving through associate, software, and now senior engineer roles.
The common thread has been reliability: making sure things work, knowing when they won’t, and building the systems to respond when they don’t.
If something I write is useful or wrong, I’d love to hear about it. You can find me on LinkedIn.