AI removed the bottleneck of writing code and exposed every other one. The math behind the productivity paradox, the five tolls between your laptop and your user, and how to replace approval queues with self-service platforms and automated guardrails.
All posts
Reliable systems are available when users need them. Reliable engineers are too. Proactivity, punctuality, clear documentation and ownership, plus a practical guide to onboarding into a new team through QA, the PO and the Tech Lead.
Most rework is not caused by bad code, but by questions nobody asked. How to prepare for refinements and discovery sessions, and which questions a backend engineer should ask before writing the first line.
Five years working remotely from Maputo with Brazilian teams taught me a new vocabulary, a relaxed way of talking that hides a demanding quality bar, and what it means to build software at the scale of a country with more than 200 million people.
Seven years in, the biggest change in how I work is not the languages or the tools. It is the shift from writing code fast to designing systems that last, and the questions I now ask before writing a single line.
Working from Maputo with teams in Brazil means my day starts five hours earlier. Here is how that time zone gap became a deep work window, what it costs at the end of the day, and the async habits that make it work.