What we've learned shipping software for growing companies: architecture, design, AI and the decisions in between.
6 notes
Latest note
Patterns that look fine at ten customers and fall apart at a hundred and how to catch them early to fix them.
Most design systems die the first time two teams need the same component to do two different things.
The gap between a compelling demo and a production feature is almost always evaluation, not the model.
Cutting scope and cutting architecture are not the same decision, and conflating them is expensive.
Most on-call pain isn't the pages, it's a rotation designed for a team five times your size.
Retrofitting accessibility after launch costs roughly ten times what building it in costs.
Stay in the loop
Product notes and engineering insights. No noise, unsubscribe anytime.
