![](/assets/artwork/1x1-42817eea7ade52607a760cbee00d1495.gif)
105 episodes
![](/assets/artwork/1x1-42817eea7ade52607a760cbee00d1495.gif)
No Compromises Joel Clermont and Aaron Saray
-
- Technology
-
-
4.9 • 7 Ratings
-
Two seasoned salty programming veterans talk best practices based on years of working with Laravel SaaS teams.
-
Why we have a separate test suite for external services
Writing tests that communicate with a third party can be a little tricky, but we've found an approach that balances speed and confidence.
In today's episode, we share that approach and talk through a strategy of how frequently to run tests that talk to the outside world.
(00:00) - Why would your tests ever talk to an external service?
(02:30) - What does it mean to have a separate test suite?
(06:00) - Keeping them separate allows different triggers for running
(07:00) - When should you run external tests?
(08:30) - You can't always know when you'll break an external integration
(11:00) - Check on a schedule?
(13:00) - Silly bit
Would you like to take 2 - 3 minutes each day to learn a little bit about Laravel? Join for free, unsubscribe any time. -
API specs aren't just for giant teams
I don't have time to write an API spec. We're not a giant team. We don't have external users of our API.
I've said all these things in the past, but in today's episode, we discuss why you should still consider writing a specification for your Laravel API.
(00:00) - Should you write a spec for your API?
(01:37) - Thinking through the requirements
(04:07) - What's in a spec?
(06:20) - Balancing detail with moving forward
(08:15) - Who is consuming the spec?
(09:30) - The spec keeps you honest
Would you like to see what over 4,000 Laravel developers like about the Mastering Laravel newsletter? It's free to sign up. -
Slowly introducing static analysis without changing everything
Maybe you've tried to add static analysis to your Laravel app and got scared away by all the errors.
In this episode we discuss how we like to introduce PHPStan to large, long-lived projects in a way that doesn't introduce a lot of risk or change.
Would you like help introducing Larastan to your project? That's one of many things we can help you with!
This episode is sponsored by Mailtrap, an Email Delivery Platform that developers love. Try for Free at MAILTRAP.IO -
Troubleshooting an empty session
Why isn't this working? It can be frustrating when something doesn't work as expected!
In this episode, we talk through a recent issue Joel had with sessions and oauth flows. There are a couple principles that apply more broadly.
Next time you're stuck on something, let us help!
This episode is sponsored by Mailtrap, an Email Delivery Platform that developers love. Try for Free at MAILTRAP.IO -
Magic methods are okay in the right context
"Magic" methods and properties show up several places in Laravel, as well as third-party packages. They can make certain things easier and less verbose, but there is a trade off. In this episode, we discuss a few different contexts where we like and avoid magic accessors.
We'd really appreciate it if you share the show with other Laravel devs.
This episode is sponsored by Mailtrap, an Email Delivery Platform that developers love. Try for Free at MAILTRAP.IO -
Should you let your admin do that?
Admins can do everything in the app, right? Today we discuss a couple reasons why you may want to consider not letting an admin have access to every single feature in your app.
🎉️ Episode 100 is a huge milestone for us. Thank you for listening!
This episode is sponsored by Mailtrap, an Email Delivery Platform that developers love. Try for Free at MAILTRAP.IO
Customer Reviews
Funny and Educational
I love how each episode is centered around a specific idea or concept. Plus the bits at the end about their personal lives or jokes can be really funny.
Entertaining!
It’s a very good podcast to listen to if you need background noise! It’s Also fun listening to my own father!