Writing an API spec is a great start, but if you're not validating that your implementation matches your spec, you're not getting the full value out of the spec. I share a story from a recent project that highlights this point.

masteringlaravel.io/daily/2025-01-17-dont-just-write-the-api-spec-validate-it-too

Don't just write the API spec, validate it too | Mastering Laravel

From: masteringlaravel.io

I love following conventions. It gives me consistency and makes my code more familiar to others. Today's tip is a story where breaking from convention actually introduced a bug into my test logic.

masteringlaravel.io/daily/2025-01-16-stick-with-dashes-in-http-headers

Stick with dashes in HTTP headers | Mastering Laravel

From: masteringlaravel.io

Sometimes in programming, it feels like you need to remember a million little facts. If you get one wrong, it can surprise you. In today's tip, I share a nice bit of feedback from a reader that gives you one more thing to remember.

masteringlaravel.io/daily/2025-01-15-how-you-return-early-matters-inside-listeners

How you return early matters inside listeners | Mastering Laravel

From: masteringlaravel.io

When you publish a Laravel tip every single day, you're bound to get something wrong now and then. Today's tip is a slight correction to a recent podcast on Eloquent, thanks to an astute listener.

masteringlaravel.io/daily/2025-01-14-ordering-by-a-relationship-in-eloquent

Ordering by a relationship in Eloquent | Mastering Laravel

From: masteringlaravel.io

I love Eloquent. It's such a productive part of Laravel. But what if Eloquent doesn't quite do what you want? Or the default approach doesn't perform well enough for your needs?
masteringlaravel.io/daily/2025-01-13-laravel-podcast-when-to-step-out-of-eloquents-comfort-zone

When to step out of Eloquent's comfort zone | Mastering Laravel

From: masteringlaravel.io