Lessons from a Project with a 2001 Commit
summary
A retrospective on a long-running project started with a 2001 commit, focusing on engineering practices that stay valuable over a ten-year span. Covers real-world lessons for building and maintaining high-load systems, challenging common microservices and ‘high-load’ myths and highlighting pragmatic approaches that endure.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:02Monolith to microservices
- 7:34Distributed systems problems
- 14:10Analytics and business value
- 17:45When microservices needed
- 24:17Premature architecture risks
- 29:59Focus on business results
- 35:16System design as skill
- 37:50Creating value not complexity
- 41:31Project architecture evolution
- 45:20Management collaboration
- 48:16Summary and Q&A
related talks
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
53m20 Years on the Rake: Failures, Outages and Lessons Learned
49mWhat Does a Legacy System Teach Us?
45mLegacy
27mTell Us Another Story Grandpa: Lessons Learned over 16 Years as a Developer
22mNotes to my younger self
28mLessons and Expierience from 15 years of Agile Coaching
40mWhat We Left Behind - 10 Valuable Skills From The 1990s