No Compromises

No Compromises

By Joel Clermont and Aaron SarayTechnology
Download on the App Store

No Compromises episodes

  • Why two databases are better than one

    Joel and Aaron discuss the benefits of having distinct databases for testing and local development. They share how this approach ensures a reliable test suite and avoids conflicts with day-to-day dev work. In the process, they reveal a simpler workflow for setting up new environments and keeping projects stable.

    • (00:00) - Why separate dev and test databases
  • (02:15) - Automating database setup with seeders
  • (05:00) - Avoiding flaky tests and migration pitfalls
  • (09:00) - Reimagining old habits with new practices
  • (12:00) - Silly bit

  • Sign up for the free Mastering Laravel newsletter
    15 min
  • Dealing with being a beginner again

    In this episode, Joel and Aaron discuss the struggles of learning new technology on a late-night side project. They share tips for handling frustration and managing expectations.

    • (00:00) - Late-night MicroPython struggles and revelations
  • (02:15) - Overcoming complex hardware and language hurdles
  • (05:15) - Balancing side projects with realistic expectations
  • (10:30) - Silly bit

  • Don't be a stranger. Check out the Mastering Laravel community.
    15 min
  • Making short demo videos count

    Joel and Aaron explore the value of using concise video demos instead of long emails or scattered screenshots. They discuss which clients benefit from quick visuals and when text is still best.

    Want to see us on camera? Join the Mastering Laravel community for our live dev calls.

    • (00:00) - Recording brief Loom demos for updates
  • (02:15) - Considering audience and communication style
  • (05:00) - Video calls vs. text-based explanations
  • (07:45) - Silly bit
  • 10 min
  • Examining test layering in multi-tenant requests

    Joel and Aaron debate how to structure multi-tenant API requests and tests. They explore the interplay between authentication, tenant headers, and different levels of validation. In the end, they reminisce about old infomercial freebies and wonder if they still exist.

    • (00:00) - Debating authentication vs. tenant header priority
  • (02:15) - Handling unusual requirements in request tests
  • (05:00) - Navigating multi-layer middleware concerns
  • (08:30) - Balancing thoroughness and test coverage
  • (12:00) - Silly bit

  • Want some advice on writing better tests for your app? Contact us.
    14 min
  • When to step outside of Eloquent's comfort zone

    Joel and Aaron explore the nuances of when to venture beyond Eloquent in Laravel applications. They discuss specific scenarios where using lower-level database tools might be necessary, while emphasizing the importance of not abandoning Eloquent entirely. The conversation provides practical insights into balancing framework features with performance needs.

    • (00:00) - Exploring when to step outside framework defaults
  • (02:30) - Handling complex sorting with related tables
  • (05:25) - Balancing Eloquent features with DB builder tools
  • (07:15) - Important considerations when dropping to lower level DB access
  • (10:00) - Silly Bit

  • Check out the Mastering Laravel community.
    13 min
  • Feature flags: Temporary tool or permanent solution?

    Joel and Aaron dive into a friendly debate about the true nature of feature flags in software development. Drawing from their varied experiences across different programming languages and environments, they explore whether feature flags should always be temporary or can serve permanent purposes. The discussion evolves from a simple disagreement into deeper insights about different architectural approaches.

    • (00:00) - Newsletter tips undergo careful peer review process
  • (02:15) - Debating if feature flags should be temporary
  • (05:25) - Different uses of feature flags across languages
  • (07:20) - Feature flags in modern Laravel applications
  • (08:35) - Silly Bit

  • Sign up for free to get those amazing Laravel tips delivered each day
    11 min
  • Deciding when to use a new piece of technology

    Ooh, something new was just announced. And I have this project coming up. It could be perfect! But should I use it?

    On today's episode of No Compromises, Aaron and Joel share a conversation they had along these lines on a recent client project and considering the new Flux library from the creator of Livewire.

    • (00:00) - Discussing potential Flux adoption in Bootstrap project
  • (01:00) - Flux explained: Livewire-based UI component library
  • (04:45) - Risk assessment of adding new technologies
  • (06:00) - Extra risk for a 1.0
  • (08:45) - When new tech might be worth the risk
  • (11:50) - Silly Bit

  • Want calm, reasonable developers like us to help with your project?
    15 min
  • Taking liberties with value objects

    Programmers love geeking out and creating specialized terms and vocabulary. Well I can do that too. In today's episode, we talk about "value objects", put our own special definition on it, and discuss when we might use these in a Laravel project.

    • (00:00) - What I mean by "value object"
  • (03:00) - Nicer to do in newer PHP versions
  • (04:00) - Main use case for value objects
  • (05:30) - Use them for everything then?
  • (09:00) - A second reason to use a value object
  • (10:45) - Silly bit

  • Sign up for our newsletter and get short, practical Laravel tips delivered fresh to your inbox.
    13 min
  • How to deal with things outside your control on a dev project

    Have you ever struggled working with a third party on one of your developer projects? How do you handle that, keeping it professional and also still able to meet your commitments?

    In today's episode of No Compromises, Aaron and Joel discuss what happened on a recent project and how they think about handling those kinds of difficulties while still having boundaries.

    And if you're looking for help on your Laravel project, get in touch!

    11 min
  • Should we use a JSON field for this?

    JSON fields can be very useful, but when is a good time to include them in your database design?

    In today's episode of No Compromises, Aaron and Joel use a couple examples from recent projects to talk through reasons they would and would not use a JSON field.

    • (00:00) - Debating JSON fields in database design
  • (03:06) - Configuration options: JSON vs. relational tables
  • (07:05) - Real-world example: label customization dilemma
  • (11:30) - Silly bit

  • Want a place to ask any question related to Laravel development? Check out the Mastering Laravel community.
    15 min

About No Compromises

From the publisher's feed

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

More shows like No Compromises

The Laravel Podcast by Matt Stauffer

The Laravel Podcast

57 Listeners

Startups For the Rest of Us by Rob Walling

Startups For the Rest of Us

698 Listeners

Darknet Diaries by Jack Rhysider

Darknet Diaries

8,055 Listeners

Notes On Work - by Caleb Porzio by Caleb Porzio

Notes On Work - by Caleb Porzio

18 Listeners

The Stack Overflow Podcast by The Stack Overflow Podcast

The Stack Overflow Podcast

62 Listeners

The Bootstrapped Founder by Arvid Kahl

The Bootstrapped Founder

35 Listeners

All-In with Chamath, Jason, Sacks & Friedberg by All-In Podcast, LLC

All-In with Chamath, Jason, Sacks & Friedberg

10,190 Listeners

Hard Fork by The New York Times

Hard Fork

5,559 Listeners

Mostly Technical by Ian Landsman and Aaron Francis

Mostly Technical

27 Listeners