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?

People in this episode

Hosts: Aaron Saray, Joel Clermont

Topics covered

• configuration management
• code documentation
• inline calculations
• software development habits
• code optimization

Keywords

• configuration files
• inline math
• code comments
• software habits
• performance optimization

More episodes of No Compromises

• How much logic is too much logic in a PHP enum · June 6, 2026 · 13 min
• Your codebase is not a museum for old code · May 23, 2026 · 14 min
• Do you actually own the code you ship? · May 9, 2026 · 15 min
• Do you actually need a multi-tenancy package? · April 25, 2026 · 14 min
• Local and production should match even for Laravel tools · April 11, 2026 · 13 min
• When weird code needs to explain itself · March 28, 2026 · 11 min