This is mostly spot on. But I believe there is a part about decreasing parallelism that is subtly wrong. The posts specific arguments against parallelism seem

This is mostly spot on. But I believe there is a part about decreasing parallelism that is subtly wrong. The posts specific arguments against parallelism seem to imply the optimal way to create shared understanding is to locate it in a single head. The issue with trite parallelism is that it creates priority inversion. The critical resource is the devs who understand the problem and the code. Trite parallelism merely occupies all the devs who understand with the task of teaching new people, thus prevents progress on diagnosing existing problems. It is however important to know that increasing the number of devs who understand an area is a postive. With increased understanding of an area, new ways to partition work can be discovered or created. Reducing the latency to correctly triage outstanding bugs is also important for re-scoping, which is somewhat more powerful than merely re-estimating.