All notes
Engineering
6 min read
The case for the boring stack
We use the same small set of tools for almost every build. Here is why, and when we break the rule.
Clients sometimes ask why we do not use the newest framework. The honest answer is that a site is an asset the client will own for years, and our job is to make it cheap to own.
What boring means
A visual editor for pages, a structured CMS for repeatable content, plain images and a handful of tested components. Nothing that needs a build server to change a headline.
When we break the rule
We reach for custom code when something cannot be done any other way, and we write it small, documented and removable. So far that has happened about once a year.
The monthly Acta
One letter a month. No spam, no eagles.
What we learned, what we shipped and one thing worth reading. Unsubscribe with a single click.