SOLID Object-Oriented Design
summary
Argues that SOLID (especially single responsibility and dependency injection) makes changing code cheap and safe, and demonstrates it by refactoring a patent-processing job: original job that calls net/FTP and ActiveRecord becomes a mockable Downloader, a reusable YAML-backed Config (metaprogrammed into accessors), and a generic FTP/SFTP downloader, with tests kept fast and green and slow external checks run via micronaut. Concrete claim: inject dependencies, split responsibilities, and the code remains flexible and reusable instead of rigid.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:03Application Changes
- 4:45Solid ObjectOriented Design
- 7:22Solid Design Principles
- 13:33Writing Code
- 14:20Ground Rules
- 18:29Resistance
- 21:53Mocking
- 31:32Refactoring
- 37:26Dependencies
- 40:21Things Change
related talks
01h 00mSOLID Revisited : The State of the Matter
32mSOLID Principles in Practice: Clean Architecture
29mSOLID and TDD, Sitting in a
01h 00mThe most dangerous phrase
24mKeynote – Michael Feathers
51mA Contrarian View of Software Architecture
43mWhat Comes After SOLID? Seeking Holistic Software Quality
56mThe Best Simple System for Now