Configuration
also: config, configs, config file, configuration file
The settings that control how your app behaves, kept separate from the main code so they can be changed without rewriting it.
Values and options that shape an application's behavior without changing its logic, such as feature switches, service addresses, limits and tool settings. Configuration lives in files (like next.config.js), environment variables, or a settings service.
Configuration is the dial on your oven: temperature, timer, fan on or off. The oven is the same machine; the settings change how it cooks.
Many "it works here but not there" problems are configuration differences, not code bugs. Asking your agent to check configuration first can save a lot of wasted fixing.
The code is fine. The problem is configuration: the production config still points to the old email provider. I'll update that setting.
Make the maximum class size part of the configuration, not written into the code, so I can change it without a new release.
Thinking configuration matters less than code. A single wrong setting can take down an app just as easily as a bug.