Like they say, there are two hard problems in programming: cache invalidation, naming things and off-by-one errors. What if I told you I know how to name things… and Laravel scopes helped me figure it out?

masteringlaravel.io/daily/2025-03-26-naming-things-is-suddenly-easier

Naming things is suddenly easier | Mastering Laravel

From: masteringlaravel.io

If a simple "if" statement will work, why would I chain on Eloquent's "when" method? I am not a fan of fancy code, but this provides much more value than I originally thought.

masteringlaravel.io/daily/2025-03-25-using-eloquents-when-method-cleans-up-code

Using Eloquent's when method cleans up code | Mastering Laravel

From: masteringlaravel.io

We work with a variety of teams each year, and it's interesting to observe patterns as to when a team is ready to bring in outside help. In this podcast episode, we explain how to know if you should bring in outside help, and how to get the most out of it.

masteringlaravel.io/daily/2025-03-24-laravel-podcast-when-to-bring-in-outside-help

When to bring in outside help | Mastering Laravel

From: masteringlaravel.io

Programmers like clever names for things. For example, we call our test doubles "mocks" and "spies". Today I talk about what the difference is and which one I like to use in my tests.

masteringlaravel.io/daily/2025-03-21-when-would-i-use-a-mock-versus-a-spy

When would I use a mock versus a spy? | Mastering Laravel

From: masteringlaravel.io

Laravel has some amazing test helpers, but I ran into some unexpected behavior recently when testing a piece of view data was null. In 4 minutes, I'll demonstrate the problem and show my solution.

masteringlaravel.io/daily/2025-03-20-video-be-careful-when-asserting-view-data-is-null

Be careful when asserting view data is null | Mastering Laravel

From: masteringlaravel.io