All Episodes
No Compromises — 157 episodes
Running AI agents on your production server is the new FTP
Why having a human partner still beats relying on AI alone
What is really inside the AI tools you blindly install
How much logic is too much logic in a PHP enum
Your codebase is not a museum for old code
Do you actually own the code you ship?
Do you actually need a multi-tenancy package?
Local and production should match even for Laravel tools
When weird code needs to explain itself
Are you testing your app or just the framework?
Being anti-hype does not mean being anti-AI
Three ways to plan an upgrade when your codebase is a patchwork
Stop doing math in your config files
What could be worse than having no tests?
Why I changed my mind about down migrations
Why senior developers feel wrong more often
Should you ever hand-format code?
Discussing different ways to model data
Read outside tech to expand your horizons
Rewriting without a map: shipping an MVP from a legacy app
A composable, versioned toolkit for Laravel projects
Should you use DTOs in Laravel?
Sunsetting a company app without loose ends
When building a UI makes more sense than bloating your seeders
Blade includes vs components: how we decide
Changing your mind about when() and unless() in Eloquent
Finding a code-review style that fits your brain
Never take hostages: give clients control from day one
Balancing test coverage without chasing 100 percent
Exploratory coding when requirements are fuzzy
Understanding how Stringable works inside Blade views
Finishing up our discussion on not having time
Why “no time” really means “no priority”
When validation can protect your app's performance
Stick with conventions and avoid overengineering your Laravel app
When to bring in outside help
Why two databases are better than one
Dealing with being a beginner again
Making short demo videos count
Examining test layering in multi-tenant requests
When to step outside of Eloquent's comfort zone
Feature flags: Temporary tool or permanent solution?
Deciding when to use a new piece of technology
Taking liberties with value objects
How to deal with things outside your control on a dev project
Should we use a JSON field for this?
A balanced approach to static analysis in Laravel apps
Why do we like testing so much?
What does it mean to "know" something?
How to approach being wrong
Where do you go when you need help?
What does it mean if someone says your app is slow?
Why we have a separate test suite for external services
API specs aren't just for giant teams
Slowly introducing static analysis without changing everything
Troubleshooting an empty session
Magic methods are okay in the right context
Should you let your admin do that?
Don't get overwhelmed by errors in your application
Does it matter how your code looks?
The life cycle of database hosting
Are you really going to need that abstraction?
Should you change application code to support a test?
What is the point of design patterns?
Move that logic out of your view
Is it worth switching to another tool?
How we use seeders in our applications
Don't just get mad at some tech, dig in and learn!
Making a case for consistency
Different approaches to upgrading to a new major Laravel version
Maybe you don't need to write code this time
Should you manage roles and permissions with a UI?
The changing value of books throughout your career
Some reasons to write a down method in your migrations
Managing a micro-manager
A couple handy features in PHPStorm
Tools should work for you, not boss you around
Harnessing that post-conference excitement
How do you tell a teammate they might be wrong?
Lots of different ways to test record creation
How do you avoid distractions?
When should you use final classes or private properties?
Is it ever ok to delay writing tests?
Should an Eloquent relationship include soft-deleted records?
Interviewing other developers like a human
The benefits of working with other developers
Changing our mind about queues in testing
Too many rules?
Keeping an open mind with other languages and tools
What we look for in a package
Blogging versus tweeting
Knowing when to use new language or framework features
Going on a bug hunt
Thinking about the user, even in the details
Why do you write your tests like that?
Avoid painting yourself into a corner
Look before you leap
Don't plan to do too much
Isolate the problem
What should I test?
Picking a strategy for translation in Laravel
Should a factory follow all business rules?
Understanding different learning styles
Sometimes it's good to be boring
What was this developer thinking??
Should you fix all bugs in a legacy project?
Learning from other communities
Uh-oh, that proof of concept is going into production. Now what?
The benefits of sharing what you learn
How to deal with interruptions
Should I write this weird code or is there a Laravel feature I can use instead?
Take time to look back and review
The benefits of testing, even under a deadline
When to calculate a value versus when to store it in the database
Should I use an event/listener or a model observer?
How we wrap up a project
Don't be afraid to change your mind
The proper way to argue
What makes a good staging environment?
Your project is not special
Planning out a week of work
A few things to watch for with Laravel policies
Onboarding a new project
Paying down technical debt
Knowing when and how to try something new
Wireframe before coding
Continuous integration doesn't have to be hard
Deciding what to build
Are your logs too noisy?
How we decide whether or not to take on something new
Are you allowed to do that?
Are you a Laravel developer or a PHP developer?
Should developers have access to production?
Pick a coding standard, any one will do
The art of asking and answering questions
Testing 1 ... 2 ... 3, let's talk testing
Guarded vs fillable, fight!
Don't ignore that pain!
Validation is your friend
Always be ready to hand off the project
Finding and fixing a performance issue
Someone said my app is slow. Now what?
How long does it take to get your project running?
Is it a good idea to install that package?
Where do I start making things better?
How long is that going to take?
Getting started with a legacy codebase
Why even review when my code is perfect?
Are you testing me?
What is the one true way to do this?
Did you just tell me to read the manual?
Do you have a clear mental model?
The best argument is no argument
What's with these flaky tests?
When should I upgrade my Laravel project?
How do you figure out why your code isn't working?
When is the right time to automate a dev task?