-
Anti-Misalignment: Nobody knows what “alignment” is
Most “alignment” efforts just react to misalignment. This talk reframes alignment as group flow, explores why misalignment is so viscerally felt, and shares practical tools to move from reactive coordination to proactive clarity and autonomy.
-
You can big bang!
Explore when rewriting code from scratch actually works and how to plan a successful, high-impact system redesign.
-
Leading a team through 0-1 product development
In this talk, we will discuss tips for leading an engineering team through developing a new product fast, especially when there are a lot of unknowns.
-
In partnership with AntithesisBuild bravely: Delivering risky projects
Learn how clear specifications and property-based testing help engineers take bolder roadmap risks, ship faster, and collaborate safely with LLMs.
-
Lessons from the other side: What your VP is actually thinking
Learn how to build a partnership with your VP by sharing unfiltered reality and gaining the context you need.
-
The altitude slider: Knowing when to dive into code vs. drive the strategy
Practical cues and rituals that help senior ICs oscillate between architectural vision and hands-on execution.
-
Are we arguing or are we architecting?
Guiding technology decisions at scale is daunting for senior ICs. Spirited debates often feel like conflict, but they're crucial. Learn to turn these clashes into collaborative, well-informed decisions. Are we arguing or architecting?
-
Engineering excellence: New product development in medical devices
Lessons from leading a seven-year development of a NextGen SPECT/CT scanner, focusing on innovation, compliance, and team leadership.
-
Reimagining the image pipeline at Squarespace
This talk explores the evolution of Squarespace's image pipeline—why change was needed, how the architecture adapted for scale and flexibility, and the unique challenges faced along the way.
-
Un-becoming the bottleneck
The biggest obstacle to team growth is often Staff+ engineers themselves. Breaking this pattern requires more than just "org-wide impact" it calls for deep, deliberate focus on growing 2-3 key engineers around you.