Keynote – Michael Feathers
summary
Argues that uniform coding standards and abstract SOLID rules often clip design context and cause trouble, citing a claimed 100x performance story where blanket rules drove a language switch; recommends replacing edicts with concrete design challenges and short checklists, using repo mining and simple questions — split this class how will this change fail who must understand it — to track longitudinal cost of choices like ORMs and make deliberate, testable design decisions.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:42Uniform coding standards pain
- 3:46Rigid standards performance pitfalls
- 5:52Design decisions metaphor
- 6:55Transition to design principles
- 9:42Design challenges with principles
- 13:31Failure and change considerations
- 15:16Longitudinal view of design decisions
- 18:04Checklists for design
- 20:51Standards to open conversations
- 21:54Industry shift design challenges
- 22:36Closing and legacy code
related talks
33mClosing Keynote
01h 03mKeynote: Abstraction Patterns
42mKeynote - Livable Code
01h 01mKeynote: Writing Software
49mKeynote: Debug your thinking
01h 10mKeynote: Strategies to Cope With Conflicting Design Patterns in C++ Development Teams
08mLightning talks – 101 Things Software Never Learnt
01h 16mKeynote 3: The Zen of Programming