Stop doing math in your config files
About this episode
The episode discusses the drawbacks of using inline math in configuration files and advocates for better documentation practices.
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?
More episodes of No Compromises
- Do you actually own the code you ship?
- 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
Explore listener stats, chart rankings, contacts and more on the No Compromises podcast page.