The strongest thing I built into Genesys UI wasn't a component — it was a habit: components that leave a space to be filled instead of reaching out and grabbing another library. Coupling is inheritance in disguise, and it scales just as badly.
When does a package belong in a monorepo, and when does it deserve its own repository? After building a design-system ecosystem, I'm convinced there's only one real rule — and a pile of convincing-looking reasons that should never drive the decision.
What I learned leading Genesys UI: why a design system is a layered ecosystem of packages, not a component library — and what that buys you and costs you.
A new chapter for an old habit: why a digital hub (again), why functional programming, and why 42.