kaal:claim:3995709-006

Confusion during code review lengthens reviews through a message escalation mechanism: more confusion produces more messages exchanged during discussion, so the review takes longer than it should.

Source quote, verbatim

that more confusion leads to an increase in the number of messages exchanged during the discussion, therefore reviews take longer.34 If there is confusion between the reviewer and the code, the code review will take longer than it should.

From

Wulf A. Kaal, How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards (2021), Code Confusion, p. 9
https://ssrn.com/abstract=3995709 · source PDF

Cite as

Wulf A. Kaal, How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards (2021). SSRN: https://ssrn.com/abstract=3995709

Holds when

reviewers encountering unfamiliar code

Classification

mechanismsupport: evidencedopen-source-and-code

Related claims

extended_by kaal:claim:4755632-023 Code reviews in legacy systems can last weeks and months, and these delays can force complete rewriting of con...

Verify

The quote above is an exact substring of the source PDF, whose sha256 is 6d77dbfb15ee86080bfde0b98089180cabafeb6defdf0f05eaaeb3cb99871e89. Extraction method: pdf-text-layer.
Attestation record: colloquium/attestations/bc717d43bfdb9a5a...json
Verify the binding yourself: curl -s https://wulfkaal.github.io/claims/3995709-006.md | sha256sum