Design systems that survive a rewrite
Most design systems die when the framework changes. The ones that last store decisions, not components.
0%
Loading Revolutionary Mindsets
Insights
Things we learned building and maintaining software other people have to live with. No listicles, no thought leadership — just what worked, what did not, and the reasoning behind it.
Lighthouse scores are a symptom, not a target. Here is the performance budget we hold ourselves to on every build, what each metric actually measures, and what gets cut first when the budget slips.
Most design systems die when the framework changes. The ones that last store decisions, not components.
Not everywhere. We mapped the places it earns its keep, and the places it quietly costs you time.
The structure we use for every project scope, and the four sentences that prevent most disputes.
Empty, loading, partial, error, offline, too-much-data. A checklist we run before any screen is called done.
Why an untested backup is a rumour, and the twenty-minute drill we run with every client before handover.
No articles in that category yet.
Stay in touch
No schedule, no newsletter-for-the-sake-of-it. We write when there is something worth writing about.