Crafting maintainable Laravel applications
summary
Slides and concrete takeaways: ten tips for maintainability, concrete numbers and tools, and code-level fixes. Claims include 20,000+ Laravel apps used Shift and a call to stay current; evidence: config files in 6.0 change configs changed 16 times in six weeks. Specific practices: prefer real‑time facades, use morphMap for polymorphics, centralize container bindings in AppServiceProvider, start with a services folder then refactor by the rule of three, prefer traits/composition over overriding core, and use SQLite memory via phpunit.xml for tests.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:00SHIFT
- 1:1520 YEARS OF CODING
- 1:53TIPS FOR MAINTAINABILITY
- 4:05ADOPT THE STANDARDS
- 7:01DEFAULT THE STRUCTURE
- 7:45parallel // hierarchies
- 9:46where // does // it // go
- 11:07MANAGING PACKAGES
- 14:24SMOOTH BINDINGS
- 17:18CONFIGURING CONFIGS
- 20:28AVOID OVERWRITING
- 24:50GROK THE FRAMEWORK
- 30:26'HONOR THE MVC PATTERN
- 34:49WRITE TESTS
related talks
39m50 Laravel Tips
48mMigrating a 15 Year Old Enterprise Application to Laravel: Lessons Learned and Opportunities Gained
21mSoftware Design Patterns in Laravel 4
54mThings Laravel Made Me Believe
36mLiving peacefully with Laravel
32mFull stack architecture
40mEngineering Complex Applications with Laravel 4
33mEnterprise Laravel