4 ms·
> At Stripe, my current project is to implement a speculative approach to testing and merging changes, this will allow us to scale merges to hundreds of commits
by educaysean 5y ago
> At Stripe, my current project is to implement a speculative approach to testing and merging changes, this will allow us to scale merges to hundreds of commits per hour while keeping the main branch green.
I don't know how to interpret this sentence. What does the author mean when they say "implement a speculative approach"? Is this something that other monorepo orgs can also adopt? Or is it specific to Stripe?
Merge conflicts seem like an area with heavy potential for headaches that arises from the use of monorepo, and I wish the author would've shared deeper insights here.
- xorcist 5y ago> Merge conflicts seem like an area with heavy potential for headaches that arises from the use of monorepo, Now you tell me! I should just split my repos and my merge conflict will go away?
- detaro 5y agoDo you really feel like that's a productive response to someone whishing for more detail?
- marcosdumay 5y agoIt's more likely that they will become independent and non-blocking. But then, "monorepos done right" tend to be quite similar to "multirepos done right", just with the tooling organized differently. So they often share problems and failure modes too.
- m12k 5y ago> What does the author mean when they say "implement a speculative approach"? My guess is that they want to speed up testing by being able to say "this PR only touches these files, and we know they are only tested by these tests, so we don't need to run all the other tests". And instead of needing to define these connections manually, it should be possible to use information from previous tests runs (although that information may be out of date depending on the changes being made, making it speculative). Anyways, just a guess
- CBLT 5y agoI'm guessing the speculative approach is https://news.ycombinator.com/item?id=19692820 https://news.ycombinator.com/item?id=19692820