Balance innovation with stability
Playing with new things is fun, but when your product code becomes the playground where you learn new things, bad patterns are unwittingly encoded and then naturally propagated over time. Often it's best to make your inexperienced mistakes in less important projects first.
Examples
- You've found an exciting new database technology that promises faster queries, but it's still in beta. Instead of adopting it right away for your primary product, you decide to use it in a small project like an internal dashboard to test things out.
Share this principle