Hear about some cool new tool or coding technique on Twitter? Great, jump right in and use it on your biggest production app! Or . . . maybe don't. We share some thoughts on how to evaluate things critically for your particular circumstances.

Do you want to blindly take our advice? Great idea! Check out our book on Laravel validation rules.

Do you always finish everything you plan on doing? Probably not, very few developers do. The problem isn't always how you work. Some of it is how you plan. We discuss several tips on how to plan for a more successful week.

Want to get notified when we release new tools, books, and articles? Sign up for our newsletter!

What do you do when you're stuck? Aaron shares a tip on how he breaks down a problem when he's feeling stuck.

Are you stuck with your Laravel/PHP project? We can help! Book a free call.

We all know we should write tests, but what should we test? Is there anything it doesn't make sense to test? We talk through a high-level approach to how we do feature testing in Laravel.

Need some help or advice on your Laravel project? We can help!

There are different ways to structure your translation assets in Laravel. We discuss how we approached this on a recent project, and why we chose the method we did.

Check out the validation worksheet we built. It may help jump start your Laravel validation rules.

Factories are really useful in tests, but could they give you a false sense of security if they don't generate models exactly like a user of your application would? We talk through some benefits and cautions to think about as you're designing your factories and factory states.

Share the love! Tell people on Twitter about the podcast.

What a surprise, Joel and Aaron have a different learning style. We talk through our different approaches to learning, and what we've found useful.

Did you like this? We'd appreciate a review or share of the podcast

Do you like to fiddle with settings? Joel doesn't. Find out why, and hear about one example where we like deviating from the defaults.

Learn more about Laravel at masteringlaravel.io

Maybe you've inherited a project and just looking at how the code is organized makes your head hurt. Before you go ripping it apart and "making it better", it can be useful to take a step back and use a more measured approach.

Want us to work with your team? Book a free call to see if we can help.

You've inherited a legacy app. It's "running fine" in production, but when you add an error reporting tool, you see hundreds of errors, warnings, and notices logged each day. What do you do?

Check out our books and courses at masteringlaravel.io