I also put everything in one repo nowadays, no matter the usage, the language etc. All is synced, and all is accessible by my LLM. There are a lot of tools to manage monorepos, and frankly most of the time you don't even need them.

▲

ffsm8 a day ago | parent | next [-]

It makes releasing software a lot more complicated.

Not a big deal if you're basically the only developer and handroll the process - but poly repositories make release and dependency management a lot more straightforward to wrangle

▲

bluGill a day ago | parent | prev [-]

Most of the time your repo is so small that you won't run into the problems of a large repo and so you don't need those tools. Don't confuse that for monorepos have no problems when they get large.

▲

genxy 20 hours ago | parent [-]

How large is large? What does large mean? More than 100GB? 2TB?

▲

bluGill 20 hours ago | parent [-]

You have the wrong measure. Large is number of parts. That is partially source files, partially projects/teams, and partially things that are conceptually not related. Likely other things as well.

It is unlikely GB/TB is ever a measure, though if your repo is that big and some people only need a subset of the repo it would be.

▲

jonjon10002 19 hours ago | parent [-]

Worked at a place (as a tech writing manager) where the monorepo was several TB and company-issued laptops all had 500 GB hard drives. It was like a rite of passage that new writers or people with new laptops would inevitably not RTFM or learn about sparse checkout and try to clone the entire repo, which was not good.

	▲	genxy 17 hours ago \| parent [-]
		Nice hazing ritual, I hope that behavior extended to other parts of the organization.