Listen Now

PHP marches forward (00:00) Upgrade strategy depends on team size (01:20) Considerations for new language features (02:33) Performance gains (03:27) Readability (04:56) How to adopt new features (06:16) Depends on the project's maturity (08:14) Upgrading for security (09:30) Silly bit (11:17) If you enjoy this podcast, we'd really appreciate help spreading the word. Share it with your fellow PHP and Laravel developers.

Think of a bug like a fun code puzzle (00:00) Don't get stuck for too long (01:22) The confusing CSV bug (02:35) Diffing the files (06:05) Digging deeper into Symfony and PHP (08:07) Getting stubborn about fixing this (11:29) Silly bit (12:26) Why would you validate your MIME types? Learn that and a whole lot more with our validation book: Mastering Laravel Validation Rules

00:16 Why do we write code? 01:39 The importance of user experience 02:54 A specific example of user-focused thinking 04:34 Choosing the most helpful HTTP status code 05:44 What if it’s an API response? 07:17 How much detail in an error is useful to a user? 08:35 Silly bit Move from competent to confident - become a better Laravel developer with the free resources available at masteringlaravel.io

1:06 - One weird pattern we’ve seen in Laravel project tests 2:23 - Can you explain why you’re doing this? 3:50 - “It’s more readable” 5:55 - Principle: learn a thing, do a thing, dissect a thing 6:30 - Is it okay to have code duplication in tests? 8:20 - How tests are different from application code 11:16 - Don’t add application code just for your tests 13:06 - Silly bit Need help building a test suite for your Laravel app or making your existing tests more reliable? Click the link and book a free call to see how we can help.

Want another set of eyes on your code? We can help! Visit our site and schedule a free call with us today. 00:16 The problem: this code works, but I don't like it 01:17 What we mean by "I don't like this code" 02:22 A specific example of code I didn't like 03:52 Code review sparks a discussion, and a solution 05:20 Principle: don't get locked in to your first approach 06:03 Principle: the benefits of code review 07:22 Don't be defensive, and the code reviewer isn't always right 08:03 Silly bit

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

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

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

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

Check out the validation worksheet we built. It may help jump start your Laravel validation rules. Maybe the World Destruction Tour isn't so crazy after all.

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

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

Learn more about Laravel at masteringlaravel.io What season are you?

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

Check out our books and courses at masteringlaravel.io

Download our free ebook 7 Steps to Securing Your Laravel App.

Check out Aaron's blog and Joel's blog for even more amazing wisdom.

Listening to us is just part of the fun. You can read what we've written too at masteringlaravel.io

Let us know if you have a question or topic you'd like to discuss on the show. Contact us with your suggestions, or just to tell us how great we're doing.

Want some help to make your Laravel SaaS better? Book a free 30 minute call.