Articles
Readings
The books behind the articles on this blog. For each one, what I took from it and where it shows up.
Teams and organization
-
Team Topologies
The four team types, the three interaction modes and cognitive load. It was the main basis for how we designed our payments teams.
Cited in Team Topologies in practice: how we designed our payments team Platform engineering: harmonize to innovate
-
Accelerate
The four software delivery metrics and the evidence that loosely coupled teams deliver better.
Cited in Team Topologies in practice: how we designed our payments team Platform engineering: harmonize to innovate
-
The Mythical Man-Month
Adding people to a late project makes it later: conversations grow faster than headcount.
Cited in Team Topologies in practice: how we designed our payments team
-
Domain-Driven Design
Bounded contexts, business areas with their own language and rules, as good candidates to be a team's home.
Cited in Team Topologies in practice: how we designed our payments team
Platforms and architecture
-
Platform Strategy
Platforms and IT services are opposites, harmonizing is not restricting, and a platform has to be treated as a product.
Technical career
-
Staff Engineer
The four ways to play the staff role: tech lead, architect, solver and right hand.
Cited in From senior to principal: the work that happens between teams
-
The Staff Engineer's Path
Three pillars of the staff role: big-picture thinking, executing large projects and leveling up the people around you.
Cited in From senior to principal: the work that happens between teams
-
High Output Management
A manager's output is the output of the team they influence. The same logic applies to staff engineers.
Cited in From senior to principal: the work that happens between teams
-
Getting Things Done
The horizons of focus, from today's task to purpose, as a picture of how far ahead each level needs to look.
Cited in From senior to principal: the work that happens between teams
-
Building a Second Brain
The horizons of perspective: each step of the ladder looks further ahead.
Cited in From senior to principal: the work that happens between teams
Software engineering
-
Extreme Programming Explained
Communication, simplicity, feedback, courage and respect: with AI the practices changed shape, the values didn't.
Cited in XP in 2026: the practices changed shape, the values didn't
Leadership and culture
-
Transformando suor em ouro
Discipline as culture, intention over form and the ego of the collective. I reread it when I started leading leaders.
Cited in Turning sweat into gold: what I reread when I started leading leaders Leaders don't just respect the culture, they carry it
-
Extreme Ownership
There are no bad teams, only bad leaders: the leader owns everything in their world, and the team's standard is what they tolerate.
Cited in Extreme Ownership: there are no bad teams, only bad leaders
-
The Dichotomy of Leadership
The follow-up: every leadership quality taken to the extreme becomes a flaw, ownership included.
Cited in Extreme Ownership: there are no bad teams, only bad leaders