Skip to content

Commit 6a48443

Browse files
committed
Improve phrasing to appease jeffbee on HN
1 parent bd99920 commit 6a48443

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

writing/2022-03-12-Monorepos-done-right.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -118,10 +118,10 @@ This is not such a problem with multirepos, as the occurrence of merge races is
118118
(among other things) proportional to the amount of changes per time unit.
119119

120120
The easiest mitigation is to serialize merges to the main branch. However,
121-
this does not scale. At Stripe, my current project is to implement a
122-
speculative approach to testing and merging changes, this will allow us to
123-
scale merges to hundreds of commits per hour while keeping the main branch
124-
green.
121+
naively serializing merges does not scale. At Stripe, my current project is to
122+
implement a speculative approach to testing and merging changes, this will
123+
allow us to scale merges to hundreds of commits per hour while keeping the main
124+
branch green.
125125

126126
## Trying to get things right from the start
127127
This is why I'm writing this post. Most monorepos I've been exposed to have a lot

0 commit comments

Comments
 (0)