The most dangerous phrase
summary
Argument claims SOLID and Scrum made sense for 1990s constraints but now cause harm: source code used to be a sellable asset, DB changes were risky so migrations, abstract classes and SRP were practical; today migrations, refactoring and CI/CD make schema and code changes deterministic. Concrete wins: htmx cuts JS dependencies from 255 to 9, build time from 40s to 5s and code size from ~20k to ~6k. Recommendation: treat SOLID as historical guidance and Scrum limits speed, prefer continuous delivery and lean product practices.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:43Why do we do what we do
- 4:42Ideas really do age
- 6:29How to break the rules
- 8:37Whats the power of technology
- 11:53Single Responsibility Principle
- 14:33Example
- 22:25Ruby on Rails
- 23:02Separation of Concerns
- 28:25Separate Concerns
- 31:59HTX
- 35:45Running out of time principle
- 41:00Changing code
- 42:15Single constraint
- 45:45Continuous delivery
- 51:14Scrum and Solid
related talks
41mIs Your Code Too SOLID?
47mSOLID Object-Oriented Design
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
37mHonest mistakes caused by shallow interpretation of SOLID
52mChaos Development: Removing software as the inhibitor of Agile
38mAgile Architecture
57mStop writing software like it's 1999!
01h 00mSOLID Revisited : The State of the Matter