Introducing 30 Days of Laravel

Hey there,

I'm writing to let you know of my newest project: 30 Days of Laravel.

The idea here is to produce 30 short, easily digestible videos that you can watch real quick during your lunch break. They'll teach small tips and tricks on PHP and Laravel, and you might already know some of them, but I'm sure you'll learn new stuff 🙂.

The goal is to send an e-mail, every day, for 30 days. It'll include the video, an in-depth explanation and documentation references.
I have yet to finish recording all videos, but I'm already releasing some previews.

If you would like to enroll on this (free) course, make sure to click this button:

And, if you want to check a sample of how it is going to look like, here's the first lesson on YouTube:

Although this one is about an "easy" subject, there are lessons already recorded about a bunch of stuff: dependecy injection, the container, blade components, testing, APIs... so make sure to check that out!

Mateus Guimarães

Read more from Mateus Guimarães

# On the last few weeks I have seen lots of discussions about speed in the Laravel community (and some other communities, for that matter) and I thought I share a few thoughts here. First, as developers I would say we are always going to think about performance — we want to write good code that is performant. Period. With that said, I also think it is easy to misunderstand where we need to make optimizations and where the problems lie. To be clear, I am thinking of a specific thread that...

I was reading some tweets about scaling and how Laravel was a bit behind other frameworks and I remembered I have a cool scaling story to tell. Jack Ellis already wrote a very interesting blog on how Fathom Analytics scaled Laravel, but my story is about different. You're about to read how we scaled to over a hundred million jobs and peaks of 30,000 requests/minute a timespan of only twelve hours, using nothing but Laravel, MySQL and Redis. First, I must give some context: in 2019 I joined a...

One very common question among people who started testing their stuff is..."Okay, now what? How do *actually* use this?" It is fairly easy to teach the basic concepts of testing, but it's really hard to teach people how to leverage testing/TDD to solve complex problems, especially with simple examples. With that said, there's no better way to teach that than test-driving a feature on a real application. Not a dummy ecommerce or blog, but an actual application that has complex features and...