From Good To SOLID: How to Become a Better PHP Developer?
summary
Claims that applying SOLID principles to a PHP codebase turns a 50+ line update method into four delegate calls, drops a migration estimate from ~30 days to 5, and isolates third‑party coupling. Shows concrete work: replacing a monolithic adapter for zoko recruits with interfaces, repositories and simple model wrappers, switching from API arrays to Eloquent objects, binding implementations once, and adding a handful of repository methods to make the local database rollout work.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:15PHP Humor
- 2:25Spaghetti Code
- 3:23The Platform
- 5:02Candidate Class
- 5:52Update
- 7:16Third Party System
- 8:50Local Database
- 9:53Code Changes
- 11:10SOLID Design Principles
- 19:06OpenClosed Principle
- 20:42Edit Part
- 21:10Change View
- 21:31Risk of Substitution
- 23:58How to Improve
- 25:22Interfaces
- 26:09Repository
- 26:37Model Classes
- 27:15Update Function
- 28:42Repositories
- 29:07Recap
- 30:34Summary
related talks
29mSolid Code
59mIntroduction to SOLID
57mRefactoring a large legacy PHP Application: a case study
58mObjects, Testing and Responsibility
28mReformat, Refactor, Replace: A practical guide for dealing with legacy software
37mHow I Accidentally Wrote the Best Code of my Career
39mClean Coding - 10+ Techniques To Clean Your PHP Code
38mCrafting maintainable Laravel applications