Keynote: Cognitive Debt is a Doubtful Guest
summary
Claim: adding powerful platforms often cuts org productivity by creating cognitive debt rather than reducing technical debt. Examples: Kubernetes is called over‑engineered and pulled in Helm, Istio and other ops baggage; Rust adds constant pointer/ownership overhead; microservices and OpenTelemetry raise hidden costs. Measured win: personal GPT use gives ~three times productivity, org gains lag. Practical checks: prefer libraries over frameworks, optimise feedback loop times and maintain dev‑prod parity so local work reproduces production.
AI-written summary · about
chapters (7)
- 0:00Introduction and keynote setup
- 1:11Productivity revolutions over time
- 3:42Cognitive debt defined and explained
- 10:30Cognitive debt in practice
- 14:43Frameworks vs libraries
- 16:51Design principles for productivity
- 21:09Q&A and closing remarks
related talks
37mKeynote - You are Load Bearing
52mKeynote: The Psychology of Code
39mKeynote - The gordian knot
39mStop Focusing on Tech Debt
41mKeynote: The Silver Bullet Syndrome Director's Cut - Complexity Strikes Back
23mCan We Please Stop Talking About Tech Debt?
27mThe human cost of development
38mFallacies of Software Development