We have such a rich ecosystem of packages in the Laravel and PHP community. But can there be too much of a good thing? What do we consider before adding a small package to our projects?

• 00:00 A healthy ecosystem of packages
• 01:02 Too much of a good thing?
• 02:48 Risks to consider
• 04:13 Other ways to share
• 05:34 Think before you promote
• 08:02 Consider the friction
• 08:39 Silly bit

Would you like help auditing the packages in your Laravel application?

Laravel has a vibrant community of people teaching and sharing what they've learned. What makes a good tip? Should you tweet or blog or both?

• 00:00 Why blogging is beneficial
• 02:43 Slowing down before you publish
• 04:30 Tips that provide value
• 08:11 Platforms can go away
• 09:36 Silly bit

Check out the new articles section on masteringlaravel.io

New PHP version! New Laravel version! So exciting! But when does it make sense to upgrade, and when does it make sense to start using new language or framework features?

• 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.

How can a bug be fun, and not frustrating? When you treat it like a puzzle. Let's walk through a recent bug with CSV mime type validation and go deep down the rabbit hole.

• 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

User experience is a term we hear a lot as developers, but it can mean different things depending on the context. We discuss a recent project where decisions around which HTTP status code to return was focused on improving the user's experience and trust in the application.

• 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

We discuss two "interesting" patterns we've observed in a number of Laravel projects. Let's take a step back and think about why we write tests the way we do.

• 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.

We've all been there: a thorny piece of code works, but it seems like there must be a better way to simplify it or make it more readable. We share one example when this happened to us, and how code review led to a better solution.

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

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.