--- title: '99% of devs DON''T UNDERSTAND Laravel...' source: 'https://youtube.com/watch?v=SuIljMDou1o' video_id: 'SuIljMDou1o' date: 2026-06-15 duration_sec: 0 --- # 99% of devs DON'T UNDERSTAND Laravel... > Source: [99% of devs DON'T UNDERSTAND Laravel...](https://youtube.com/watch?v=SuIljMDou1o) ## Summary The video argues that most Laravel developers ignore built-in features like service containers, Eloquent relationships, and queues, making their code unnecessarily complex. The speaker shares personal experience and urges a shift from 'how to build this' to 'what's the best way to do this.' ### Key Points - **Common Mistake** [0:00] — 99% of devs ignore Laravel's built-in features, making their lives harder. - **Manual Validation** [0:41] — Developers write manual validation in controllers instead of using Laravel's features. - **Service Containers** [1:04] — Laravel's container auto-wires dependencies, reducing setup code from 50 lines to just working. - **Eloquent Relationships** [1:34] — Using eager loading and custom relationships can reduce DB queries from over 100 to under 10 per page. - **Queue System** [2:07] — Laravel queues with Horizon process tasks in background, improving user experience and providing monitoring. - **Performance Impact** [2:34] — 53% of mobile users abandon sites loading over 3 seconds; queues help avoid delays. ### Conclusion Stop reinventing the wheel; leverage Laravel's built-in tools to write cleaner, more maintainable code. ## Transcript Look, I'm just going to say it. If you're building Laravel apps the way most tutorials teach you, you and probably 99% of devs watching this are making your lives 10 times harder than it needs to be. I'm talking about fundamental approaches that Laravel literally gives you for free. But 99% of developers just ignore them. Stay with me for the next few minutes because what I'm about to show you will completely change how you think about building web applications. I've shipped a few Laravel apps in the past couple of years and honestly, for the first two projects, I was doing it completely wrong. I was writing hundreds of lines of code that Laravel was ready to handle for me. My controllers were bloated. My code was repetitive and deployment was a nightmare. Then I locked in and discovered what I'm about to share with you. Here's what I see a lot online. Developers treating Laravel like it's just PHP with extra steps. They write manual validation in controllers. They skip service containers. They ignore policies and gates. And they manually handle things like rate limiting and caching. Why? Because most tutorials focus on getting something working fast, not on building it the Laravel way. you end up with code that's technically functional but impossible to maintain or scale. And this is exactly what we're trying to avoid. Let's first talk about service containers and dependency injection. Instead of manually creating objects and passing dependencies everywhere, Laravel's container does this automatically. Imagine you have a payment service that needs a logger, a database connection, and an API client. Most people create all of these manually in every controller method. With Laravel's container, you just type hintit in your constructor and boom, everything is wired up automatically. Your code goes from 50 lines of setup to just working. This follows the dependency inversion principle from solid design, making your code infinitely more testable and flexible. Here's another one. Eloquent relationships used correctly. Everyone knows has many and belongs to, but barely anyone uses the powerful stuff. You need all users who made a purchase in the last 30 days and spent over $100. Most developers write a nightmare of joins and wear clauses. What the HELL IS EVEN THAT? >> Laravel lets you do this with warehouser loading in one readable line. But here's the kicker. You can create custom relationship methods and use with count to avoid n plus1 query problems that kill performance. Laravel debug bar shows that apps with proper eager loading can reduce database queries from over 100 per page to under 10. And here's the one that separates hobby projects from production grade applications. Laravel's Q system combined with horizon. You have a user uploading a profile picture. Most developers process it immediately while the user waits. That's terrible. With Laravel Q's, you add implement should Q to your job class and it runs in the background. The user gets instant feedback. Horizon gives you a dashboard to monitor jobs, balances load, and retries failures. This is infrastructure that companies pay thousands for, and Laravel gives it to you out of the box. Google's research shows that 53% of mobile users abandon sites that take over 3 seconds to load. So why do 99% of developers miss this? Because we're taught to code, not to take advantage of frameworks. We solve problems from scratch. But with Laravel, the problems are already solved. The shift you need is this. Stop asking, "How do I build this?" and start asking what's the best way to do this. Here's what I want you to do right now. Open your latest Laravel project and find one place where you're doing something manually, just one. Refactor that one thing using Laravel's built-in features. That's it. And if you want to better understand Laravel, you must first hone your PHP skills. And the best way to do that is to create cool unique projects using Code Crafters, the sponsor of today's video. They are the most rated GitHub repo, and that's for a good reason. Their platform gives you access to unique projects that will help you stand out from the competition without the clown shoes and nose. Want to build an HTTP or DNS server from scratch? Check. Hell, you can even craft your own version of Git. All while others are still struggling to center that annoying div in their to-do app. You can start some projects free of charge, and if you use my link in the description, you can get yourself a whopping 40% off. So, hurry up. This was Codehead with yet another tech rant. If you enjoyed it, please leave a like and subscribe. Lights out.