Convention over configuration
When building software systems and frameworks
What Does “Convention over configuration” Mean?
Follow established conventions and defaults instead of requiring explicit configuration for everything. Sensible defaults reduce decisions, code, and cognitive load. Only configure what truly differs from the norm.
What Happens When You Break It
Requiring configuration for everything creates verbose code, decision paralysis, inconsistency across teams, slow onboarding, and maintenance nightmares from endless custom configurations.
Benefits of Following This Rule
Following conventions speeds development, reduces code volume, improves consistency, simplifies onboarding, enables team coordination, and lets developers focus on actual business logic instead of configuration.