The observations and inferences here about cycle time, throughput, and behaviour of teams matches with my experience very well. Pair and mob programming are a better way to approach the "review a draft PR early and often" technique because the putative reviewers are also engaged in contributing.<p>There may be tooling advances as well to support these modes, as the repo clone or fork is currently either per-user or centrally hosted. Shared dev env capabilities such as provided by IDEA IntelliJ are a step in the right direction, though I fear security vulnerabilities from it.