"Hoodwinked by the Terrible Trivium"
summary
Argues that $25M of early failure taught why brilliant engineers create brittle, one-person processes and that $1.3T digital spend (IDC says $900B fails) really fails from unsustainable toil. Describes a terrible trivium of tempting quick fixes, shows a bespoke toil calculator, adoption of Harness plus Terraform modules and archetyped pipeline-as-code, and reports removing maintenance windows, deployment calls and outages while raising production confidence — the orchestration worked where scripts alone did not, hence template library and orchestration vs automation.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:29Simplifying CI/CD matters
- 4:14Brilliant talent challenge
- 7:03Measuring toil and scaling
- 8:46Automation vs orchestration
- 10:13Rewarding group benefit
- 11:35Sustainable cloud platforms
- 13:41Archetypes for scaling CI/CD
- 15:46Removing human toil
- 16:47Empathy in CI/CD
- 17:49Closing and key takeaways
related talks
39mConfessions of a Systems Engineer: Learning from My 20+ Years of Failure
27mYellow Brick Code: Lessons from The Wizard of Oz on Enhancing DevEx
05m5 ways to burnout your engineers
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
50mFallacies of Software Development
50mRiding the wave of complexity
22mChoosing Failure
38mSimplicity: The Key to Software Success