Choose Boring Technology
Dan McKinley's argument for spending a company's few innovation tokens deliberately and preferring well-understood technology with known failure modes.
Canonical text: https://boringtechnology.club/.
The argument
- We all get a limited number of innovation tokens to spend; early on in a company's life, we get maybe three.
- Software that's been around longer tends to need less care and feeding than software that just came out.
- Pick the smallest set of tech that covers our problem domain, and lets us get the job done.
- Adding the technology is easy, living with it is hard.
- You should have a process for adding technology to your stack that involves talking to other humans.
- Prefer technology that's well understood, with failure modes that are known.
- Prefer things that let you focus your attention on what really matters.
- Happiness comes from shipping stuff.
Facts
- Maintainer
- Dan McKinley
- Status of the text
- stable
- Listing
- listed, not yet claimed
Read with
-
Basics of the Unix Philosophy
Eric Raymond's seventeen rules distilling the Unix design tradition, alongside Doug McIlroy's original maxims, from The Art of Unix Programming.
-
The Twelve-Factor App
Twelve factors for building software-as-a-service applications that are portable, declarative and ready to scale, written at Heroku from experience operating hundreds of thousands of apps.
Badge
[](https://manifesto.md/boring-technology/) Maintainers claim a listing with a pull request setting listing: claimed, or a yes on the listing issue.