If You’re Not Shipping, You’re Not a Leader
summary
Concrete examples: moved a JBoss‑based DurEcoEmos server off the factory floor to avoid $16,000/minute downtime; built a Node + Cheerio DOM‑scrape backend that proved a UI concept but angered owning teams; ran a one‑hour microfrontend demo that cost a Medline contract; shipped an eight‑hour POC and deployed to edge in ~100 milliseconds; enabled a non‑engineer to build a mini‑CRM on the cloud platform; uses module federation and AI to turn individual shipping into team shipping.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:39Leadership begins with impact
- 3:43Manufacturing IT and remote fixes
- 6:31Legacy systems and unowned platforms
- 8:57UI strategy without code authority
- 10:41Executive leadership and wrong shipping
- 12:47Founder bottlenecks and team scaling
- 17:18Sales lessons and leadership frameworks
- 18:40Revisiting rooms with AI tools
- 19:21Enabling teams with POCs
- 21:08Measuring impact beyond deployment
- 21:50Decomposing work for faster shipping
- 23:13Empowering non-technical members
- 24:15Hiring for domain judgment
- 24:36Summary: Ship one, enable one
related talks
25mEgoless Engineering
37mReal Developers Ship (a.k.a Tenets for Software Delivery)
39mShip fast!
47mGo Faster: Remove the Inhibitors to Innovation
34mAn Engineering Team Where Everyone is a Leader
33mAn Engineering Team Where Everyone is a Leader
28mHow To Finish What You Start: Lessons From Actually Shipping..
38mJust Ship It!