What we learned from our first year
Fewer services, more boundaries. A look back at the decisions we would make again — and the two we would not.
Wanjiru Mwangi
Engineering Manager
1 min read
On this page
A year ago this team was three people and a whiteboard. Here is what held up.
Boundaries over services
We split code into modules with strict import rules long before we split anything into services. Most of those modules will never need to be services.
Write the contract first
Every feature starts as a Zod schema both sides import. Arguments about shape happen once, in review, instead of in production.