Oh No I'm Stuck! A Guide to Detangling a Complex Codebase
summary
Claim: a messy monorepo untangles if one maps, reverse-engineers and documents actual call paths. The method uses UI+file‑structure mapping, running tests through AppMap to generate sequence diagrams, isolating modules like the Strapi admin guided‑tour, and spotting the app.tsx entry point and state handlers. Steps: collaborate, run tests to observe calls, read PR history, run and rewrite small modules, then document and peer‑review the resulting module stories so others can pick them up.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:57Motivation
- 4:50Foundation elements
- 8:43From tourist to local
- 13:46Systems thinking
- 17:43Demo: AppMap mapping
- 27:16Documenting knowledge
- 28:43Codebase structuring
- 29:48Summary
related talks
28mI've Fallen Into a Large Codebase and I Can't Get Up!
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
23mMonorepos & Spaceships - Navigating successfully through Code and Cosmos
19mEscaping Chaos: Strategies to Move from Polyrepo to Monorepo
24mHow to prevent a rewrite
29mModularity and Monorepositories
46mExploring the power of monorepos: When and why to use them
23mUntangling Your Dependencies: A Pattern for a Well-Knit JavaScript Project