#workpost

So, while so many of the staff members are out this week, i'm taking the opportunity to train up interns and other junior devs with some semblance of "calmness" around the remote office.

So without any further context:

Whats the general consensus on Mono Repos 'round these parts?

We have a diverse git layout of repositories that are all inter-linked and the distributed nature of the config / app code / etc. is startling to these jr devs.

Is a monorepo a good fix?

Follow

@chuck There's not one answer, there's a trade-off.

The overhead of separate repos (versioning, dependencies, duplicate (or inconsistent) packaging/tooling) is almost always a mistake if the same team owns all the repos.

If you're large enough to have multiple, fully independent workstreams, the overhead of building everyone else's code for a simple change is a mistake.

But in my experience, the former is more common than the latter.

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!