Monorepo from Day One

Day one of a new startup would seem to be a great moment to adopt a monorepo, with the beautiful, endless, green field of opportunity stretching to the horizon. But what happens if that startup already has more than thirty engineers eager to get started, and an ambitious deadline in the immediate future?

We'll cover the highs and lows of going from a blank slate to more than 80 projects in just two months, including building a strong culture around naming, aggressive plugin adoption, and the risks of "bottleneck" dependencies.