When I was a contractor at Google I was surprised by the mono repo, but really liked it. Scaling issues aside, it makes sense having all dependencies in one rep

When I was a contractor at Google I was surprised by the mono repo, but really liked it. Scaling issues aside, it makes sense having all dependencies in one repo. I thought of having a mono repo at home because many of my projects are inter related but instead I spent some time with a library setup. For Common Lisp, I used a pattern in one of Zach’s blogs to have one central repo for all of my personal Common Lisp code that is configured as a root for Quicklisp. Any of my code can be quick loaded no matter where I am working. Really simple but it makes it possible to write small utilities/libraries and reuse them for whatever I am doing. I sort of do the same for Python, writing a setup.py for each small project or library to install globally, including appropriate executable scripts. This also allows me to combine small things easily. I am not yet set up to do this yet for my Haskell projects but it is on my todo list.