Podcasts with Joel Clermont
From the Podcast Index, this is the very latest data from the podcast:person feature of Podcasting 2.0. Read more details
No CompromisesEpisode: Is the traditional code review workflow holding you back?
No CompromisesEpisode: Write better requirements or pay for it later
No CompromisesEpisode: Which layer of caching does your slow app actually need?
No CompromisesEpisode: Where do credentials end and configuration begin in your env file?
No CompromisesEpisode: Running AI agents on your production server is the new FTP
No CompromisesEpisode: Why having a human partner still beats relying on AI alone
No CompromisesEpisode: What is really inside the AI tools you blindly install
No CompromisesEpisode: How much logic is too much logic in a PHP enum
No CompromisesEpisode: Your codebase is not a museum for old code
No CompromisesEpisode: Do you actually own the code you ship?
No CompromisesEpisode: Do you actually need a multi-tenancy package?
No CompromisesEpisode: Local and production should match even for Laravel tools
No CompromisesEpisode: When weird code needs to explain itself
No CompromisesEpisode: Are you testing your app or just the framework?
No CompromisesEpisode: Being anti-hype does not mean being anti-AI
No CompromisesEpisode: Three ways to plan an upgrade when your codebase is a patchwork
No CompromisesEpisode: Stop doing math in your config files
No CompromisesEpisode: What could be worse than having no tests?
No CompromisesEpisode: Why I changed my mind about down migrations
No CompromisesEpisode: Why senior developers feel wrong more often
No CompromisesEpisode: Should you ever hand-format code?
No CompromisesEpisode: Discussing different ways to model data
No CompromisesEpisode: Read outside tech to expand your horizons
Ditching HourlyEpisode: Joel Clermont - The Pros And Cons Of Selling Software Development As A Subscription
No CompromisesEpisode: Rewriting without a map: shipping an MVP from a legacy app
No CompromisesEpisode: A composable, versioned toolkit for Laravel projects
No CompromisesEpisode: Should you use DTOs in Laravel?
No CompromisesEpisode: Sunsetting a company app without loose ends
No CompromisesEpisode: When building a UI makes more sense than bloating your seeders
No CompromisesEpisode: Blade includes vs components: how we decide
No CompromisesEpisode: Changing your mind about when() and unless() in Eloquent
No CompromisesEpisode: Finding a code-review style that fits your brain
No CompromisesEpisode: Never take hostages: give clients control from day one
APIs You Won't HateEpisode: Generating API Specs can be Painful, with Joel Clermont from Mastering Laravel
No CompromisesEpisode: Balancing test coverage without chasing 100 percent
No CompromisesEpisode: Exploratory coding when requirements are fuzzy
No CompromisesEpisode: Understanding how Stringable works inside Blade views
No CompromisesEpisode: Finishing up our discussion on not having time
No CompromisesEpisode: Why “no time” really means “no priority”
No CompromisesEpisode: When validation can protect your app's performance
No CompromisesEpisode: Stick with conventions and avoid overengineering your Laravel app
No CompromisesEpisode: Why two databases are better than one
No CompromisesEpisode: Dealing with being a beginner again
No CompromisesEpisode: Examining test layering in multi-tenant requests
No CompromisesEpisode: When to step outside of Eloquent's comfort zone
No CompromisesEpisode: Feature flags: Temporary tool or permanent solution?
No CompromisesEpisode: Deciding when to use a new piece of technology
No CompromisesEpisode: Taking liberties with value objects
No CompromisesEpisode: How to deal with things outside your control on a dev project
No CompromisesEpisode: Should we use a JSON field for this?
No CompromisesEpisode: A balanced approach to static analysis in Laravel apps
No CompromisesEpisode: What does it mean to "know" something?
No CompromisesEpisode: Where do you go when you need help?
No CompromisesEpisode: What does it mean if someone says your app is slow?
No CompromisesEpisode: Why we have a separate test suite for external services
