No Compromises

Do you ever finish writing a test and wonder if it is actually proving anything about your code or just confirming that Laravel works?
In the latest episode of the No Compromises podcast, we discuss how to tell the difference between tests that validate your logic and tests that merely exercise the framework.
We share a practical gut check: if you cannot make a test fail by changing something in your own application code, it probably should not be in your test suite. We also look at this idea from the other direction, asking whether the code being tested is something we actually wrote.
We also dig into why testing validation rules is worth the effort even when they feel boilerplate, how feature versus unit test style shapes these decisions, and why the real goal is simply getting to a place where your tests help you ask the right questions.
Join the Mastering Laravel community at https://masteringlaravel.io/community
00:00 Are we testing code or framework
02:00 Joel metric for framework-only tests
05:15 Bottom-up testing perspective by test type
07:36 Why validation rules still deserve tests
10:40 Silly bit

Does everyone need to have an AI hot take right now, or is there value in waiting until you actually know what you're talking about?

In the latest episode of the No Compromises podcast, we discuss why it took us 147 episodes to finally tackle the topic of AI.

We dig into the tension between wanting to speak with authority and feeling pressure to share before you're ready. Aaron makes the case for building deep knowledge first, while acknowledging that people at every stage of the learning curve play an important role in moving the community forward.

We also talk about how fast the AI landscape is shifting, why zooming out matters more than memorizing details, and why being a slower mover isn't something to apologize for.

(00:00) - Why we haven't talked about AI yet

(01:00) - Building deep knowledge before sharing opinions

(02:30) - AI moves faster than JavaScript frameworks

(04:30) - Zoom out before sweating the details

(06:15) - Every stage of the learning cycle matters

(07:45) - Silly bit

Want to get that new AI tip we mentioned? Sign up for the Mastering Laravel newsletter.

When your project has the same thing done three different ways, how do you bring everything up to date with a consistent approach?
In the latest episode of the No Compromises podcast, we discuss different strategies for tackling upgrades when parts of your codebase are multiple versions behind.
We walk through two main approaches and weigh the tradeoffs for both the developer doing the work and the person reviewing it.

(00:00) - Setting up the upgrade scenario

(02:15) - Approach one: upgrade each area to current

(04:00) - Why the reviewer's experience matters too

(07:30) - A third approach neither one expected

(09:00) - Silly bit

Want help upgrading your Laravel project?

Ever feel the urge to write out calculations in your code to make them "self-documenting"?
In the latest episode of the No Compromises podcast, we discuss why inline math in configuration values is a habit worth breaking.
Aaron argues that if a value never changes, there's no reason to calculate it every time. A well-placed comment can explain how you got the number without the unnecessary overhead.
We also cover how comments can clarify units like seconds versus milliseconds, why this thinking applies beyond config files, and how questioning small habits can improve your code overall.

(00:00) - How many seconds is five minutes?

(01:45) - The problem with inline config math

(03:45) - Using comments instead of runtime calculations

(05:30) - Why questioning habits improves code

(07:00) - Silly bit

Want a second set of eyes on your Laravel project?

Found a cool package on Laravel News? But how do you know if it's actually worth installing?
In the latest episode of the No Compromises podcast, we discuss what we look for when evaluating third-party packages before bringing them into a project.
Aaron makes the case that what he finds in the tests folder is essentially a deal-breaker: no tests means no trust, but leaving default example tests behind is somehow even worse. Tests reveal whether the maintainer thought through edge cases and serve as living documentation when the README falls short.
We also cover the other signals we weigh: GitHub stars, download counts, issue responsiveness, and how quickly maintainers keep up with new Laravel versions.

(00:00) - Evaluating packages you stumble across

(01:30) - Why leftover example tests frustrate Aaron

(03:45) - Tests as documentation and edge case proof

(05:00) - Checking issues and Laravel version history

(08:00) - Silly bit

Want to work with us on your project?