Monorepo Explained

Reflecting on the well-known Monorepo tools out there, and it seems that most of them focus on task automation and orchestration: caching of runs and doing that fast. Those things are obviously very important, but I miss the perspectives of reusing code and also the local development experience (aside from running tasks like automated tests and such).

From my point of view, the main reason to have code in a Monorepo is to be able to easily share code between different projects and have the code & tools at your fingertips while writing new code. This is where the Polylith Architecture comes in, focusing on this particular thing. There's tooling support for Clojure and Python as of this writing.