3 ms·
Most of you don’t need a monorepo, the same way most of you don’t need, well, half the shit peddled in the tech Instagram (conferences, meetups, mediums, blogs,
by runawaybottle 5y ago
Most of you don’t need a monorepo, the same way most of you don’t need, well, half the shit peddled in the tech Instagram (conferences, meetups, mediums, blogs, hn).
You just don’t need that stuff, there’s like 20 of you on a team and at best your app probably sucks and barely has users, and if it does have users, it’s probably some trivial bullshit.
You’re all a bunch of ordinary folks, so stop fucking up the workplace with your identity crisis. No, you are not an elite engineer, you are Bob, the guy who goes home every day and watches Netflix/plays video games.
- detaro 5y agoThe nice thing is, you can replace "monorepo" with "multiple repos" in your comment and it's just as believable a statement arguing for avoiding trouble with coordination/packaging etc.
- runawaybottle 5y agoWell, it’s something that needs to be said about a lot of things. Life is a balance and now days in tech I see the pendulum swinging way too far to the other side.
- sergiomattei 5y agoSurprisingly, a monorepo is much easier for smaller teams and individuals to work with. As someone who has been maintaining a React and Django app solo for the past three years, two repositories or more is too much cognitive overhead to work with. Never doing that again. Monorepo are easier for small apps.
- runawaybottle 5y agoPutting stuff in the same repo is a pragmatic idea. Going into the monorepo isolated self contained publishable app/package is a whole ‘nother thing, along with all the tooling necessary to make it work seamlessly. You want to put stuff in the same repo, that’s fine. What’s with all the other bullshit?