No Compromises

Have you ever added a method to an enum and then wondered if you just turned it into something it was never meant to be?
In the latest episode of the No Compromises podcast, we discuss where to draw the line when adding methods and logic to PHP enums.
We trace the evolution from magic strings to constants to interfaces, and explain why enums were the missing piece PHP needed all along.
We also cover when label methods and data structure helpers belong on an enum, why Eloquent queries cross a line, and how to avoid turning a simple enum into a bloated helper class.

(00:00) - Why magic strings and constants fall short

(01:43) - How PHP enums replaced interface constants

(02:26) - What methods belong on an enum

(06:58) - The rule for keeping enum methods focused

(10:44) - Silly bit

Join developers who think carefully about clean code decisions in the No Compromises community.

Have you ever opened a file to make a quick change, only to find dozens of lines of commented-out code making it nearly impossible to understand what's actually running?
In the latest episode of the No Compromises podcast, we discuss why keeping dead code around is slowing your whole team down.
We make the case that commented-out or unused code creates real confusion when searching a codebase, whether you are a new developer, a consultant, or even an AI agent trying to understand what is actually in use.
We also cover why Git is all the safety net you need, how Git bisect can recover deleted code you thought you might need someday, and why the fear of deleting code is almost always unfounded.

(00:00) - Why commented-out code slows everyone down

(02:03) - How dead code creates false search results

(05:10) - Dead code costs you more with AI agents too

(05:55) - How Git bisect helps you recover deleted code

(10:08) - When commenting out code is actually fine

(11:45) - Silly bit

Join the conversation and share how your team handles dead code in our No Compromises community

When a tool hands you a working solution, how much do you really need to understand about why it works?
In the latest episode of the No Compromises podcast, we discuss whether developers still care about understanding the code they ship, or whether that expectation is becoming a relic of the past.
We explore why knowing the "why" behind a solution isn't just about curiosity. It's about having enough domain knowledge to ask better questions, push back on bad answers, and ultimately produce better work.
We also walk through a real code review example involving a tricky Eloquent query, talk through the pressures that pull developers away from digging deeper, and consider what separates a line cook from a chef in how we approach our craft.

(00:16) - Are developers losing the habit of asking why

(02:16) - How AI changes the copy-paste-and-move-on cycle

(05:25) - Learning by accident while reading the manual

(06:24) - The Eloquent query neither of us could explain

(12:16) - Silly bit

Join a community of developers who still care about understanding the code they ship.

Ever feel like a project requirement says "we need multi-tenancy," and you're not even sure what that means in your specific context?
In the latest episode of the No Compromises podcast, we discuss how to evaluate multi-tenancy needs before committing to an architectural approach.
We break down what multi-tenancy actually means, from separate databases to custom domains and per-tenant configuration, and why the real question isn't which package to use, but whether you need one at all.
We also explore when hand-rolling a simple solution beats adopting a full package, what legal and compliance requirements can force your hand, and why this is one of those decisions that's genuinely hard to undo later.
00:00 Defining what multi-tenancy actually means
02:11 Different ways to structure multi-tenant systems
03:44 When separate databases are truly necessary
04:57 Questions to ask before choosing an approach
08:25 Package vs. rolling your own trade-offs
11:30 Silly bit
If you want guidance on decisions like these, check out our code review service to get expert eyes on your architecture.

Ever installed a Laravel package locally and immediately accessed it, only to wonder later whether your access controls are actually working in production?
In the latest episode of the No Compromises podcast, we discuss why tools like Telescope and Horizon behave differently in local environments versus production, and why that inconsistency is a problem worth solving.
We make the case that developer convenience should never come at the cost of security confidence. If your gate logic cannot be exercised locally, you cannot truly trust it is protecting your production environment.
We also dig into how Aaron worked around the issue by overriding the package's service provider logic, and why Laravel has since made this easier to handle cleanly.

(00:00) - Why local and production environments should match

(01:42) - How Telescope's gate logic behaves differently locally

(03:01) - The risk of untestable access control logic

(07:53) - How Aaron overrode the service provider to fix it

(10:23) - Silly bit

(00:00) Why local and production environments should match
(01:42) How Telescope's gate logic behaves differently locally
(03:01) The risk of untestable access control logic
(07:53) How Aaron overrode the service provider to fix it
(10:23) Silly bitOur courses took the production hits so your app doesn't have to.