The Gentle Monorepo - Ship Faster and Collaborate Better
summary
Dexter migrates incrementally from separate repos to a single Python monorepo by starting with fat bases, sharing one root pyproject.toml and a locked dependency set, and extracting small reusable components. Dependency management uses UV, repository structure and lightweight build logic follow polyith, and import/governance checks live in a techtoml policy enforced by tag/tech. Reported outcomes include faster reuse across forecasting trading and battery products, fewer divergent package versions, and a claimed months‑of‑work savings on one product.
AI-written summary · about
chapters (16)
- 0:00Monorepos and shared code pain
- 3:59What is a monorepo
- 5:44Starting monorepo cheaply
- 8:37Dexter use case
- 10:02Polyith architecture
- 13:50How components work
- 15:14Managing deps with UV
- 16:40Building deployable projects
- 18:09Step-by-step monorepo setup
- 18:52Early learnings and collaboration
- 21:22Scaling to multiple teams
- 23:06Enforcing rules with TAC
- 25:54Initial concerns and tooling
- 26:57Measuring business impact
- 29:01Current challenges and future work
- 30:24Q&A
related talks
19mKeynote: Why Monorepos
29mMonorepos, are they right for you?
19mEscaping Chaos: Strategies to Move from Polyrepo to Monorepo
30mPoly Monorepos, the Best of the Two Worlds
19mMonorepos: Any Size Fits All
05mHigh Speed Monorepos with high quality DX
23mMonorepos & Spaceships - Navigating successfully through Code and Cosmos
41mHandling Monorepos Today