# Review quality `kaal:entity:review-quality` **Status.** derived This node is assembled mechanically from the 8 claims that carry the concept tag `review-quality`. It is a roster of what the corpus says under this term. It is **not** an adjudicated definition: no single statement here has been ruled canonical, and no first-appearance call has been made. Read the claims and judge for yourself. ## Every claim under this term 8 claims across 4 works, 2021 to 2024. **2021** - [3995709-003](https://wulfkaal.github.io/claims/3995709-003) [empirical/evidenced] -- Patch size degrades multiple dimensions of code review performance at once: comment density per reviewer falls as patches grow, the quality and amount of contribution is affected, and the time required to provide significant contributions increases. > found that comment density by reviewer decreases as patches increased. 18 Accordingly, the quality and amount of contribution is affected by patch size.19 And, patch size increases the time required to provide significant contributions.20 Wulf A. Kaal, How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards (2021). SSRN: https://ssrn.com/abstract=3995709 - [3995709-004](https://wulfkaal.github.io/claims/3995709-004) [failure/evidenced] *(failure mode)* -- Code review effectiveness is undermined by heavier review loads, because reviewers with longer review queues become overwhelmed and are more likely to submit poor quality code evaluations. > another study found that code reviewers with longer review queues tend to get overwhelmed and are more likely to submit poor-quality code evaluations.22 Therefore, modern code review effectiveness is undermined by heavier review loads. Wulf A. Kaal, How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards (2021). SSRN: https://ssrn.com/abstract=3995709 - [3995709-007](https://wulfkaal.github.io/claims/3995709-007) [failure/evidenced] *(failure mode)* -- Code confusion produces blind approval, where a reviewer hopes a co-worker knows what they are doing and approves a change without understanding it, which can result in further bugs and delayed production. > blind approval may occur when a reviewer hopes their co-worker knows what they're doing and blindly approves a change.36 Blind approval can result in further bugs and delay production. Wulf A. Kaal, How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards (2021). SSRN: https://ssrn.com/abstract=3995709 - [3995709-009](https://wulfkaal.github.io/claims/3995709-009) [failure/evidenced] *(failure mode)* -- Feedback in modern code review is deficient in both timeliness and substance: receiving feedback in a timely manner is developers' number one reported challenge, and the feedback that arrives is often not insightful because reviewers focus on insignificant details rather than larger issues. > Moreover, even when developers finally receive feedback on their code change, it is often not insightful or helpful. For example, the study also found that some reviewers focus on "insignificant details rather than larger issues."43 Wulf A. Kaal, How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards (2021). SSRN: https://ssrn.com/abstract=3995709 **2024** - [4734750-023](https://wulfkaal.github.io/claims/4734750-023) [failure/argued] *(failure mode)* -- Code reviews in legacy firms are often highly subjective, and without crowd controls that subjectivity produces suboptimal review outcomes because no single developer will agree on a given set of code and its intended functionality. > Code reviews in legacy code review firms are often highly subjective which leads to rather suboptimal outcomes without crowd controls. Wulf A. Kaal, Code Review DAO (2024). SSRN: https://ssrn.com/abstract=4734750 - [4755632-017](https://wulfkaal.github.io/claims/4755632-017) [mechanism/argued] *(failure mode)* -- The more hierarchical the code review process, the lower the quality of the reviewed code, and the same holds for barriers to entry: hierarchy and entry barriers together degrade code quality. > The more hierarchical the code review process is, the lower is the quality of the reviewed code. Wulf A. Kaal, AI Learning - Decentralized Governance to Optimize Human Output Datasets for AI Learning (2024). SSRN: https://ssrn.com/abstract=4755632 - [4755632-018](https://wulfkaal.github.io/claims/4755632-018) [failure/argued] *(failure mode)* -- Hierarchical review produces an anchoring failure: the first reviewer in the hierarchy gets the highest priority and follow-on reviewers merely add minor upgrades, so adding reviewers does not add the independent scrutiny that would raise code quality. > in the legacy review process, the first reviewer within the hierarchical structure of the code review process often gets the highest priority and is often merely followed with minor upgrades by follow-on reviewers. Wulf A. Kaal, AI Learning - Decentralized Governance to Optimize Human Output Datasets for AI Learning (2024). SSRN: https://ssrn.com/abstract=4755632 - [4957318-010](https://wulfkaal.github.io/claims/4957318-010) [failure/argued] *(failure mode)* -- Sunset provisions fail on their own terms when the mandated reviews are not conducted thoroughly, because laws then either expire or continue without proper scrutiny, which defeats the purpose of the mechanism. > Moreover, if the necessary reviews are not conducted thoroughly, the effectiveness of sunset provisions is undermined, and laws may expire or continue without proper scrutiny, defeating the intended purpose of these mechanisms. Wulf A. Kaal, The Future of Law - Dynamic Web3 Governance (2024). SSRN: https://ssrn.com/abstract=4957318 ## Verify Every claim above resolves to a record carrying a verbatim source quote, the sha256 of the source PDF, and a preformatted citation. Nothing here asks to be taken on trust. curl -s https://wulfkaal.github.io/entities/review-quality.md | sha256sum **Canonical form.** This markdown file is the canonical hashed representation of this entity node. Its sha256 is the content hash.