No Compromises

Have you ever had someone review your pull request, make changes without telling you, and just merge it in?
In the latest episode of the No Compromises podcast, we discuss whether the traditional code review workflow still makes sense in a world where AI tooling lets developers move faster than ever.
Aaron shares two real situations where a reviewer fixed and merged code without discussion, and we dig into why the lack of communication is the real problem, not the act of fixing things itself.
We also get into commit strategies, how friction in reviewing someone else's changes kills the learning, and why well-worn workflows deserve a fresh look when the tools around them have changed.

(00:00) - When a reviewer merges your PR without asking

(03:31) - How we handled it differently with time pressure

(05:43) - Should the reviewer just fix it and merge?

(08:02) - Too many commits create friction for the author

(13:44) - Silly bit

Get the kind of dev insights that make you rethink everything, delivered to your inbox via the Mastering Laravel newsletter. Your team is not the only one figuring this out. Join the conversation in the No Compromises community.

Have you ever handed off a feature request with barely any detail and expected the developer to just figure it out?
In the latest episode of the No Compromises podcast, we discuss why writing clear requirements is one of the most valuable things a business can do before development starts.
We make the case that even imperfect requirements beat none at all because they determine where the discovery happens, closer to the finish line rather than somewhere in the middle of the country.
We also cover why letting AI write your requirements for you is a trap, and how AI can help you review and cross-check requirements instead. And why the more detail you put in upfront, the less money you spend on surprises later.

(02:53) - Good requirements let you build start to finish

(05:10) - Imperfect requirements still beat having none

(07:36) - Why AI should not write your requirements

(09:09) - Using AI to cross-check requirements instead

(10:46) - Silly bit

Have a messy real-world project you're working through? Join the No Compromises community and talk it through with other developers.Subscribe to the Mastering Laravel newsletter for practical insights that help you communicate better with your development team.

When someone says your app is slow and you need caching, do you actually know which layer of caching they are talking about?
In the latest episode of the No Compromises podcast, we discuss the many different forms caching takes in a Laravel application and why reaching for the cache facade is not always the answer.
We walk through caching from the outside in, starting with edge caching via Cloudflare, moving into Laravel's cache facade for third-party API calls, and all the way down to memoization with the Once helper for expensive in-request calculations.
We also make the case that storing data in a database table can be a perfectly valid caching strategy, and that the right question to ask is not whether to cache but what kind of caching actually fits the problem.

(00:17) - Why caching means different things to different people

(02:04) - Edge caching with Cloudflare explained

(05:33) - When a database table beats the cache facade

(07:45) - Memoization with the Laravel Once helper

(09:19) - Silly bit

We have seen every caching mistake in the book. Our code review will find yours.Get practical Laravel tips like these delivered to your inbox every day by subscribing to our newsletter.

Have you ever fixed a failing test by adding a variable to phpunit.xml and moved on, not thinking twice about whether that was actually the right call?
In the latest episode of the No Compromises podcast, we discuss a real pull request disagreement about where environment variables belong and why it actually matters.
We draw an important distinction between credentials and workflow configuration in your env file, and why that difference should determine exactly what goes into phpunit.xml and what stays out.
We also get into why zeroing out API keys and hostnames in your test environment is not optional, and how a small oversight in one PR can quietly expose your tests to real third-party services.

(00:00) - A real PR disagreement about phpunit.xml

(01:07) - Credentials vs workflow config in your env file

(03:17) - Why Aaron is glad his tests failed

(04:49) - How to properly isolate third-party test keys

(07:25) - Silly bit

Come talk through decisions like these with developers who care in the No Compromises community.

Have you ever let an AI agent run commands on your production server because you were stuck, telling yourself it would be fine?
In the latest episode of the No Compromises podcast, we discuss why giving AI agents access to your production environment is as reckless as the bad old days of FTPing code straight to your server.
We make the case that AI agents are non-deterministic and carry no responsibility, which makes them far more dangerous than a developer making a manual mistake on a live server.
We also cover why you should never blindly run complex chained commands that an agent suggests, how to verify what your agent is actually doing, and why a little friction in your workflow is worth the safety it buys you.

(00:00) - FTPing to production is still wrong in 2026

(01:50) - Running Tinker on production is no better

(02:28) - AI agents on production servers is even worse

(07:11) - How to verify what your agent is actually doing (move from 07:00)

(11:03) - Silly bit

Stop letting non-deterministic tools make deterministic mistakes in your codebase. Get a code review.
Subscribe to our newsletter and get practical Laravel tips delivered to your inbox every day.