3 ms·
I agree with most of TFA. However, I urge everyone to start with a monorepo. Splitting a single project (developed by one team) into multiple repos will serious
by fuzzy2 5y ago
I agree with most of TFA. However, I urge everyone to start with a monorepo. Splitting a single project (developed by one team) into multiple repos will seriously slow things down later. I've seen it happen.
- Hackbraten 5y agoIt gets really bad when two repositories depend on one another, and you forget to track which commits are meant to work together.
- erik_seaberg 5y agoDon’t rely on atomic commits when you don’t have atomic deploys. If X and Y are each running on multiple machines, you must plan for new X interacting with old Y and vice versa, because that is going to happen at least while you are rolling the change out or back. This even goes for a Javascript app talking to backend hosts.