No Compromises Joel Clermont and Aaron Saray

We've talked about coding standards before, but this time we approach it from a slightly different angle. Does the way you're code is formatted affect your ability to understand it? Brains are interesting things.
Is your code slower than you'd like? We specialize in Laravel performance optimization and we can help! Contact us to discuss.

You launched a hobby project and then it starts to get some traction. What next? How do you get a more solid foundation under your app when it comes to database hosting? In this episode, we discuss the common phases we see a database go through during an app's life.
And if you'd love some help moving your database or tackling performance issues, give us a call!

Interfaces are a great tool for writing maintainable applications, but it is possible to go "too far" with abstraction. Or maybe, it's a bad use of time to write an abstraction up front before you really know you need it. We discuss some trade-offs and examples.

(00:00) - Life before interfaces in PHP

(02:30) - Going too far with interfaces

(04:45) - A discussion with payment gateways

(07:30) - Abstracting the database as another trap

(09:15) - Laravel makes good use of interfaces

(10:05) - Silly bit
Need some perspective on your Laravel project? We offer a code review service. Get in touch to learn more.

When you're writing a test it can be so tempting to just "tweak" some app code to make it easier to write that test, but we discuss why that might not be a good idea. We also talk about some app changes while writing tests that are beneficial to the overall project.

(00:00) - Sometimes changing code makes testing easier

(01:30) - Different types of code changes

(02:45) - An example with Laravel jobs

(04:30) - A time when it's okay to change code while testing

(08:50) - Avoid problems by writing tests earlier

(09:30) - Silly bit
Don't "compromise" on testing. See how we can help level up your Laravel project.

Do your eyes glaze over when someone mentions singletons or factories? We'll try to not to be boring as we explain the benefits of design patterns.
Sign up for our free Laravel newsletter and learn something new in 2 minutes or less.

Ever feel like your Blade views are getting too logic-heavy? What logic belongs in the view, and what logic would be better somewhere else? We use a recent PR discussion to talk through these points.

(00:00) - Trying to keep logic out of the Blade view

(02:00) - Using the simplest form of logic

(03:45) - Business logic doesn't belong in the view layer

(04:15) - Condition moved into the controller

(05:20) - Secondary benefit of testing
Check out the Mastering Laravel YouTube channel