Musings on OOP, Agile and The Unbearable Clarity of Being
summary
The talk examines Object-Oriented Programming and Agile practices by analyzing large open-source projects (Linux kernel, Inkscape and others) to show that many planned abstraction points—virtual interfaces and subclass hooks introduced years ago—are rarely used and runtime polymorphism is minimal. It argues that implementations change little while business logic evolves, that Inkscape’s virtual interfaces added in 2006 see almost no subclasses, and that the Linux kernel remains largely procedural C, concluding Agile provides guidance but not guaranteed scalability of architecture.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 7:05OOP origins and evolution
- 12:30Flexibility versus rigidity
- 18:55OOP reuse effectiveness
- 27:10Psychological benefits of OOP
- 34:20OOP future reflections
- 40:00Q&A
related talks
38mAgile, Craftsmanship, DevOps and other monsters [...]
48mCreativity Before & After Agile
38mPolyglot Agile
53mIntentional Code - Minimalism in a World of Dogmatic Design
52mFinding the Beauty in the Digital Brick
47mGrowing Up Agile
34mHow do our ideas about coding affect the software we create?
51mSoftware Archeology and The Code Of Doom