We Killed These Things With Fire
summary
Argues technology moves in cycles not a straight line, with concrete examples: mainframe patterns reappearing as cloud architectures, the 2010 shift to larger screens driven by teens not a single device, and the hard numbers on migration costs — 2¢/GB egress leading to petabyte ≈ $20,000 — plus a real case: a government Hadoop cluster for Treasury where cloud transfer and runtime costs offset promised savings. Recommends testing value by measuring cost, developer productivity, and operational stability before migrating.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:31When should you modernize
- 7:17How does technology advance
- 9:06The story of mobile phones
- 13:14Teenagers and mobile phones
- 14:51Technology matures
- 16:45Line of all differences
- 18:34Reference points
- 22:30mainframes
- 23:23minicomputer
- 27:59mainframe
- 29:41saving money
- 31:16cyclical technology
- 33:08testing assumptions
- 35:18cannibal code
related talks
43mMigration to the Cloud, DevOps Perspective
25mPlatform Engineering for Modern Data Infrastructure
57mCloud Adoption Patterns
46mWhen the CFO Comes Knocking: Our Journey to a Cost Efficient Data Platform
19mDoing FinOps Right: Stories of (Anti)Patterns and Spendthrift Architectures
05mContinuous cost optimization as a never-ending process
44mFrom Metal to the Cloud: Challenges and Lessons from Agile Infrastructure in Complex Environments
30mWhy most technology migrations fail (and what we've learned along the way)