SOLID Design Principles
summary
Claim: applying SOLID makes code easier to extend maintain and understand; demonstrated with Laravel techniques: custom form requests for validation repositories and an interface for swapping data stores a factory for payment types and interface segregation for ducks. Concrete outcomes include moving validation and persistence out of controllers so a store method drops from ~10 lines to 2, a payment system that adds new gateways without modifying existing code and a repository interface + binding to swap databases
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:26Working on legacy code
- 2:31Working on a startup product
- 6:03The purpose of SOLID design principles
- 8:15Single Responsibility Principle
- 14:12Open/Closed Principle
- 21:10Liskov Substitution Principle
- 28:24Interface Segregation Principle
- 31:58Dependency Inversion Principle
- 40:03Final Thoughts
related talks
32mDemystifying Design Patterns: A Practical Guide for Developers
45m'Writing code that lasts'...or writing code you won't hate tomorrow
57mCore Software Design Principles for Programmers
34mBe SOLID my Tests
37mOrganizing Code in Laravel
42mPatterns that pay off
32mDesign Pressure: The Invisible Hand That Shapes Your Code
44mNaming Things