The Case for Boring Technology

Innovation tokens

Dan McKinley coined the concept of "innovation tokens", the idea that every team has a limited budget of novel technology they can introduce before operational complexity overwhelms them. Most teams overspend this budget dramatically.

A new database, a bleeding-edge framework, a custom build system. Each one is an innovation token. Spend them all at once and you end up debugging the infrastructure instead of building the product. The goal isn't to avoid new technology entirely; it's to be deliberate about where you introduce it.

What boring actually means

Boring technology doesn't mean bad technology. PostgreSQL is boring. It's also one of the most powerful and reliable databases ever built. Express.js is boring. It has a decade of battle-tested middleware and an answer to nearly every problem on Stack Overflow.

// "Boring" doesn't mean writing boring code.
// It means the tools get out of your way:
app.get('/api/users', async (req, res) => {
  const users = await db.query(
    'SELECT id, name FROM users WHERE active = $1',
    [true]
  );
  res.json(users.rows);
});

The most productive teams I've worked with share a trait: they pick the most well-understood tool that solves the problem and move on. They save their creativity for the product, not the stack. That's not a lack of ambition. It's discipline.