The Engineercation Loop
by David Singleton • Chief Technology Officer at Stripe
Responsible for guiding Stripe's engineering and design teams for over five years. Previously spent over a decade at Google as VP of Engineering. Known for operationalizing high-craft engineering cultures at scale.
🎙️ Episode Context
David Singleton dissects Stripe's unique engineering culture, explaining how they maintained a product-minded engineering team that delayed the need for Product Managers for years. He details specific internal rituals like 'Friction Logging' and 'Engineerications' that operationalize their core value of being meticulous, while sharing how they balance 99.999% reliability with deploying changes 16 times a day.
Problem It Solves
Prevents engineering managers and CTOs from losing touch with the reality of their own development tools and deployment processes.
Framework Overview
A management practice where leaders clear their schedule to act as an Individual Contributor (IC) for a set period, pushing actual code to production.
🧠 Framework Structure
Clear the Calendar: Block 3-4 days en...
Find a Buddy: Pair with an existing e...
Ship Real Value: Pick a small but com...
No Special Treatment: Go through the ...
Log & Share: Keep a friction log of t...
When to Use
Once a year for senior leaders, or within the first 6 months for new Engineering Managers.
Common Mistakes
Doing 'toy' projects that don't touch production, or allowing meetings to creep back into the schedule.
Real World Example
David Singleton learning Ruby (which he didn't know) to ship a feature to production, aided by a buddy named Ajhja.
I'll clear several days... join a team, pick up a small task, hopefully a small feature that we can get all the way from start to finish in production and do that going through the exact experience the team has.
— David Singleton