Axioms of building a “boring” system

From a presentation from Percona. This should be on every developer’s wall:

1. If it worked 10, 20, 30 years ago, it is worth considering.
2. If a crisis makes you come alive, you have your priorities wrong.
3. If you are working on urgent system problems, it’s not a boring architecture.
4. You should be working on exciting new things that serve your customers and are otherwise unimportant.