Post #3110178

@swelljoe@mas.to and that's the thrust of it, right? You either decrease your engagement with and understanding of the code, or you still bottleneck on that engagement (review). And you can juice "output" by dropping the review requirement in the report that's supposed to show "productivity gains," and then backpedal it with loading up more review and human engagement on the other report that's put out to try to counter the drop in quality from the first method.