kanu666

3 ms·

1.
by kanu666 4y ago
Sorry, there is a quote from the article: "Kudos to other members of the Source Control team — Alex Sadleir, Wesley Li, Adam Murray, Matthew Chhoeu — who work on improving git performance at Canva" So I assume 5 people working spe
2.
by kanu666 4y ago
Git staring to break at 200-300 engineers pushing into it. Scaling git would take 200 more :)
3.
by kanu666 4y ago
Thanks for the clarification. How many people work on Developer Productivity in total and what is the percentage from the total engineering headcount?
4.
by kanu666 4y ago
Usually it is considered good proportion to start with to be 10% to work on a Developer Productivity and it should increase to 15% as company grow. But regarding source control it really depends on the approach: if you are on polyrepo - the
5.
by kanu666 4y ago
Sure, and what next? So considering that on big projects CI/CD may take up to an hour (in one of my projects it took 4 hours) the feedback loop would be great
6.
by kanu666 4y ago
Of course, you shouldn't start a project from 10 repos. But the downside is while you live in a single repo all the tooling get tuned to work with a single repo. And then there is no way to go multi-repo when you need to. So advice wou
7.
by kanu666 4y ago
If you don't have a couple of hundreds engineers who would write a custom file system for git (Microsoft), or who would take an existing source control system and nearly fully rewrite it (Facebook), or who would write a custom source c
8.
by kanu666 4y ago
But that's what those responses are all about: git doesn't scale, so don't use it if you need scale. If there are no tools that scale available, then change the approach so you don't need face this scaling problem at all
9.
by kanu666 4y ago
But in the monorepo you almost never can do the change in a single commit as it will cause incompatibilities during gradual deployment
10.
by kanu666 4y ago
How would you do refactoring over monorepo if you have sparse checkout?
11.
by kanu666 8y ago
Don't mix up downsides of multirepo and bad composition of your microservices