Based in Europe. Available worldwide.

// blog

Blog

Thinking about frontend architecture, design systems, and the decisions that compound.

7 min read

Component API Design: The Decisions That Compound

Every prop you add is a maintenance commitment. Every abstraction you choose shapes how engineers think about your UI. Here's how I approach component API design when the components need to work across teams, frameworks, and brands.

web-componentsapi-designarchitecture
Read →
10 min read

The Monorepo Migration Playbook

Moving from scattered repositories to a monorepo is one of the highest-leverage infrastructure changes a frontend team can make. It's also one of the easiest to get wrong. A step-by-step approach from someone who's been through it.

monorepotoolingmigration
Read →
8 min read

Design Systems at Scale: Governance Without Bureaucracy

The hardest part of a shared component system isn't building it. It's making sure it stays useful as teams grow. Here's how I think about governance that enables rather than restricts.

design-systemsgovernanceweb-components
Read →
8 min read

The Real Tradeoffs of Micro-Frontends

Micro-frontends promise team autonomy and independent deployments. But the costs are real and often underestimated. After implementing this architecture at scale, here's my honest assessment of what you gain and what you pay for it.

micro-frontendsarchitectureweb-components
Read →
7 min read

When to Build Your Own Component Library

Reach for Radix? Fork shadcn/ui? Go with native web components? The answer depends on your team size, your platform constraints, and how much you actually need to own.

component-librariesweb-componentsarchitecture
Read →
6 min read

Performance Budgets That Actually Work

Most performance budgets fail because they're set once and forgotten. Here's a framework for budgets that stay relevant and actually prevent regressions in production.

performancecore-web-vitalstooling
Read →