Configuration supplies input that changes an application's behavior without changing or recompiling its source code. This keeps one implementation adaptable across experiments, environments, and delivery stages. section 1.3.7 section 8.1
Changing a counter without recompiling
A counter can read an INC environment variable at startup. Running `INC=2 go run counter.go` makes it increment by two; invalid input falls back to one. The same pattern suits database connections, password salts, client endpoints, and log levels. section 8.1
A practical configuration loader layers values so operators can start with safe defaults and override them deliberately:
- Start with the default configuration. section 8.2.3
- Load a supplied configuration file, retaining defaults for missing fields. section 8.2.3 section 8.3.1
- Apply environment variables, then let command-line flags take precedence. section 8.2.3
Loaded settings can select implementation paths as well as values. For example, a configured client URL switches an API from a static translation service to a remote client, allowing QA and development to proceed in parallel. section 8.3.2
