this post was submitted on 05 Dec 2025
78 points (95.3% liked)
Programming
23738 readers
342 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
On the other hand, using ordinary tools like find and grep are exactly what I like about monorepos! Yes, they may take a while, but at least I know I'll find a file or code that I'm looking for!
With multi-repos I'm constantly searching, but not finding where a particular piece of code comes from. Yes, it's from library X, but where there heck does that live? Now I really can't use ordinary tools. I have to rely on coworkers, docs, or GitLab to search for where a piece of code is actually defined.
there is a size of monorepo where that becomes infeasible ;)
Yeah, I'm sure. It's not something I would do frequently. My work had us on beefy desktops. But, I was totally fine with letting find+parallel+grep run for 30 minutes in the background while I searched docs or messaged people on slack. Depending on your team, getting a response from slack could easily take 24 hours so. Eh.
The other thing I liked to do is directly edit the libraries in the monorepo! No need to figure out how hack some random decency manager. You have the code! Just edit and build!