Trusted Data Apps for the Agentic Data Cloud, powered by Looker
cloud.google.com·7h ago
System Design
Martin Fowler·13d ago·5 min read
Bliki: Sensible Default
TL;DR
A Sensible Default is a flexible guideline in software development that suggests practices like using version control, which can be adapted based on context. It emphasizes reassessing these defaults regularly to ensure they remain effective.
✦ Why It Matters
Adopt Sensible Defaults in your projects and be ready to justify any deviations based on context.
Key Takeaways
- Use version control as a starting point for projects.
- Separate UI logic from domain logic for better maintainability.
- Automate deployment pipelines to streamline processes.
- Regularly reassess practices to ensure they fit current contexts.
Full Summary
Sensible Defaults are recommended practices in software development that serve as a starting point when no specific constraints are present. Examples include using version control, separating UI logic from domain logic, and automating deployment pipelines.
Unlike 'best practices', which imply a rigid adherence, Sensible Defaults encourage flexibility and context-based adjustments. The term was popularized by Evan Bottcher at Thoughtworks, highlighting the need for teams to be familiar with these defaults and their limitations.
Regular reassessment of these defaults is crucial, aligning with agile principles that advocate for continuous improvement. Thoughtworks has documented these defaults in a playbook, reinforcing their effectiveness across various projects.