No Compromises

Joel Clermont and Aaron Saray

Two seasoned salty programming veterans talk best practices based on years of working with Laravel SaaS teams.

  1. Do you actually need a multi-tenancy package?

    25 APR

    Do you actually need a multi-tenancy package?

    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 means02:11 Different ways to structure multi-tenant systems03:44 When separate databases are truly necessary04:57 Questions to ask before choosing an approach08:25 Package vs. rolling your own trade-offs11:30 Silly bit If you want guidance on decisions like these, check out our code review service to get expert eyes on your architecture.

    14 mnt

  2. 11 APR

    Local and production should match even for Laravel tools

    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.

    13 mnt
  3. When weird code needs to explain itself

    28 MAR

    When weird code needs to explain itself

    Have you ever looked at a colleague's code and thought, "This is clearly wrong," only to find out it was actually a well-reasoned workaround for a tricky bug? In the latest episode of the No Compromises podcast, we discuss what happened when Aaron reviewed Joel's code and couldn't make sense of a pattern spread across multiple Livewire components. The code wasn't bad, it was solving a real UX flicker bug in an older version of Mary UI. But without context, it looked like a mistake and nearly got rejected. The fix wasn't just refactoring; it was giving the workaround a proper home: a trait with a descriptive name, clear method names, and thorough documentation explaining the bug, the reason for the pattern, and when it can eventually be removed. We also talk about why "the explanation is in the PR note" isn't good enough, how AI coding agents can unknowingly propagate patterns they don't understand, and why strange code deserves to look strange, on purpose. Explore Mastering Laravel resources to deepen your understanding of patterns like these. 00:00 The confusing code review that started this01:15 Flagging the unclear pattern across components03:54 The Mary UI toast flicker bug explained05:45 Naming, documentation, and protecting the whole team09:30 Silly bit

    11 mnt
  4. Are you testing your app or just the framework?

    14 MAR

    Are you testing your app or just the framework?

    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 framework02:00 Joel metric for framework-only tests05:15 Bottom-up testing perspective by test type07:36 Why validation rules still deserve tests10:40 Silly bit

    13 mnt

  5. 28 FEB

    Being anti-hype does not mean being anti-AI

    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.

    10 mnt

  6. 14 FEB

    Three ways to plan an upgrade when your codebase is a patchwork

    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?

    10 mnt

  7. 31 JAN

    Stop doing math in your config files

    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?

    9 mnt

  8. 17 JAN

    What could be worse than having no tests?

    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?

    9 mnt
Lihat Semua (151)

Mengenai

Two seasoned salty programming veterans talk best practices based on years of working with Laravel SaaS teams.

Informasi

  • Kreator
    Joel Clermont and Aaron Saray
  • Tahun Aktif
    2020 - 2026
  • Episode
    151
  • Penilaian
    Bersih
  • Hak Cipta
    © No Compromises, LLC
  • Situs Web Acara
    No Compromises

Mungkin Anda Juga Suka