What AI coding tools generate, what they can’t transfer, and how engineers at every level can tell the difference
José Silvaaka Zé Pedro
Architect of code, builder of teams, refactor addict, test addict, interface fan, hobbyist inventor, coffee enthusiast. Born in Portugal, living in Ireland, citizen of the world.
My path from software developer to architect has been paved with countless "aha!" moments, each one a story worth telling. From discovering the joy of automating away tedious tasks to experiencing the thrill of seeing a distributed system scale flawlessly under load, I've learned that the most valuable insights often come from reflecting on these experiences and sharing them with others.
These days, I help craft technology visions that marry cloud-native architectures with exceptional developer experiences, but I'm equally passionate about documenting the learning journey that got me here. Through my writing, I explore the human stories behind technical decisions, the practical analogies that make complex systems understandable, and the pivotal moments that shape how we build and evolve technology.
What excites me most isn't just solving architectural challenges. It's about unpacking the "why" behind our decisions and sharing those insights with fellow developers and architects. I believe the best learning happens when we examine not just what we built, but how we thought through the problems, what we discovered along the way, and how those experiences shaped our approach to future challenges.
At heart, I'm still that curious developer who gets excited about elegant solutions. Whether I'm sketching out system architectures, mentoring emerging technical leaders, or crafting stories about the human side of technology, I'm driven by the belief that sharing our learning journeys makes us all better builders.
Notes from the climb: essays on systems, teams, and the human side of building.
How drift into failure, organizational forgetting, and the quiet physics of entropy turn well-built resilience into an illusion
What platform teams become when agentic coding tools can build anything
Why the skills that got you to base camp won’t get you to the summit, and how to acclimatize before the altitude sickness hits
Individual competence and systemic compliance are different things. Conflating them is where cloud governance falls apart.
Why feature flags and kill switches are not the same thing, and what happens when teams confuse them
The discipline of walking toward discomfort and what resistance training taught me about engineering growth
Why health checks must verify capability, not liveness, and how services can protect themselves through threshold-based monitoring
Why the most productive engineers optimize for immersion, not just elimination of distractions
How high-performing teams achieve synchronized autonomy through shared understanding, not constant coordination