"Turtles all the way down: Abstractions and when we should use them"
summary
Presents a concrete model: three abstraction types — explain it better, sweep under the carpet, and reuse — with examples: using requests and kubernetes as clarifying abstractions, and a Twilio-era platform that built loadbearing wrappers over AWS which later became costly to unwind. Recommends using existing libraries like requests or cloud SDKs, keep reuse narrowly scoped, treat optionality as a smell, favour small composable pieces, and avoid a single generic request method that ripples changes across a service.
AI-written summary · about
chapters (10)
- 0:00Abstractions introduction
- 1:54Context in abstraction advice
- 4:01Defining abstractions
- 7:21Three abstraction types
- 12:39Abstraction examples
- 15:55Abstractions in practice
- 18:24Reuse risks
- 21:09Over-abstraction pitfalls
- 25:25Rules for abstractions
- 26:50Q&A
related talks
36mOn the Spectrum of Abstraction
19mFinding Your Abstraction Sweet Spot
24mPlatform Abstractions an Asset or Liability? - Let’s Understand the Abstraction Debt Trap
07mA New Kind of Abstraction
17mThe Myth of Perfect Abstractions
26mThe Power Of Small Abstractions
38mKeynote: Abstractions Breed Intuition
41mArchitecture Isn’t Kubernetes