Scott Triglia at LeadDev West Coast 2023
summary
2016 core-system rewrite faces two straight weeks of game‑breaking rollouts and one senior engineer leaving then after a year and a half the migrated system works but in a different form. Advocates installing guardrail metrics or simpler rumble strips for early warning, writing a five‑item path back to green, cataloging surviving components and lessons, and testing guiding principles across other projects. The claim is clear: decide how to lose deliberately, preserve wins, and use downtime to garden future success.
AI-written summary · about
chapters (7)
- 0:00Project failure in 2016
- 5:23Project off track
- 10:19Failing gracefully and communicating
- 14:51Trust and documenting successes
- 15:54Long-term project setbacks
- 20:28Mindset and leadership
- 24:01Closing and Q&A
related talks
40mWhy your best engineers should look after the worst systems
59mTech leadership, one year after
30mJames Stanier, Winter Wi, Janet Balneaves a panel discussion at LeadDev London 2023
36mWhat’s next for senior developers? The IC track missing manual
21mGrow-thrive-make a difference: Leading through uncertainty
48mPanel Discusson: Road To Staff/Principal Engineer
25mHow to Drive Cross Team Techincal Changes
44mThe long strange trip of a senior developer