Sooner or later Quote by Michael T. Nygard
![“It should never be possible for an administrator to break objects associations inside the application [he's talking about Spring dependency injection]. That's just wearing your guts on the outside. Whenever possible, keep production configuration properties separate from the basic wiring and…” quote by Michael T. Nygard](https://sms4smile.com/quotes/img-quotes/ae5/michael-t-nygard-51500_sooner-or-later_it-should-never-be-possible-for-an-admin_3065838.jpg)
““It should never be possible for an administrator to break objects associations inside the application [he's talking about Spring dependency injection]. That's just wearing your guts on the outside. Whenever possible, keep production configuration properties separate from the basic wiring and plumbing of the application. They should be in separate files so the administrators do not accidentally edit internals. [...] Mixing them is the equivalent of putting the ejection seat button next to the radio tuner. Sooner or later, something bad will happen.””
About This Quote
Source Book: Release It! Software Architecture and Deployment, 2014
Separating configuration from code prevents accidental system failures caused by admin errors.
In simple terms: Keep settings apart from core code.
Key Takeaway
Is config separate from code.
Themes
software development
operations
security
Mood
cautious
practical
Type
technical
advisory
When to use this quote
- deployment pipelines
- admin training
- policy enforcement
Key Concepts
configuration management
dependency injection
system resilience
Questions to Reflect On
- What safeguards can you implement to keep config isolated?
- How do you balance flexibility with safety?
A Different Perspective
Mixing can lead to hidden bugs and security risks.
