Listen "Making a case for consistency"
Episode Synopsis
We see a lot of different projects, but it's pretty rare to find one that's well-documented and internally consistent. Why does that matter? And how can you make things more consistent without spending a lot of time on it?(00:00) - We like keeping things tidy in our projects
(01:20) - Have a README, please
(03:30) - Is there a business case for consistency across projects?
(05:30) - An example with Docker build speeds in CI
(06:50) - Consistency in naming business concepts
(09:45) - Silly bit
Short, practical Laravel tips delivered fresh to your inbox. Sign up today!
More episodes of the podcast No Compromises
Why I changed my mind about down migrations
03/01/2026
Why senior developers feel wrong more often
20/12/2025
Should you ever hand-format code?
06/12/2025
Discussing different ways to model data
22/11/2025
Read outside tech to expand your horizons
08/11/2025
Should you use DTOs in Laravel?
27/09/2025
Sunsetting a company app without loose ends
13/09/2025
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.