Laravel
Laravel Best Practices: Writing Laravel That Lasts
Intermediate•
Laravel•
22 lessons•
November 13, 2026
About the author
Davor MinchorovThis course fixes the habits that make Laravel codebases hard to change, one at a time, in a single codebase: a hotel's reservation system. It opens on a controller that has taken reservations since launch and cannot be reused once reservations start arriving from a second source. Each lesson takes one habit, such as an observer that saves the same row four times or Auth::user() inside a service, shows what it costs in that code and replaces it. The last lesson ships the import for that second source on the same code the web form runs, with a test that never touches HTTP.
Laravel Controllers and the Second Caller
Laravel Observers: Saving the Same Reservation Four Times
Laravel Eager Loading From the Model
Laravel Accessors That Run Queries
Laravel Query Builder for Reports, Not Eloquent Loops
Laravel Select and Pluck Instead of Every Column
Laravel whereHas Instead of a Collection Filter
Laravel Controllers Calling Other Controllers
Laravel Auth::user() Inside the Use Case
Laravel Dependency Injection vs Facades and app()
Laravel Traits for Business Rules
Laravel Resource Controllers That Never Get Split
Laravel Folder Structure Is Not an Architecture
Laravel Command Bus for a Use Case Without a Shape
Laravel Mass Assignment Straight From the Request
Laravel Validation Is Not Enough
Laravel API Design: One Endpoint Doing Four Things
Laravel Form Request Shared by Create and Update
Laravel DTOs Instead of Arrays for Everything
Laravel Queued Mailables That Carry Eloquent Models
Laravel Value Objects Instead of Primitives
Laravel Console Commands: The Second Caller Ships