Tag
An influential essay arguing that companies should favor mature, 'boring' technology for most problems, saving limited 'innovation tokens' for areas of true differentiation. It emphasizes the importance of known failure modes and global optimization over novelty.
The article argues that teams should choose boring, well-understood technology for reliability, while being free to innovate in development practices like TCR (test && commit || revert), which are easier to adopt and abandon without long-term maintenance burden.