Thank you, it does help. I almost went the monorepo route but for some reason
thought I'd have one project.clj file with one giant list of dependencies.
Having a monorepo but with different dependency sets makes a ton of sense and I
think would have been much easier to manage.
‐‐‐
I've been happy using a monorepo with boot, and a build.boot with many building
blocks that can be mixed and matched for many deployables (uberjars in my case).
In my build.boot I define my internal blocks, but also defs for external deps
like eg postgres and grpc. That way I have one place for
This is somewhat of a retrospective -- so please bear with me. I've had the
privilege of working on a clojure project for a couple of years now, and have
accumulated some 15-20k lines of clojure code. I'm taking a little time to
look back over what has worked for me and what hasn't in terms
