# kaal:claim:3995709-009

**Claim.** 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.

**Type.** failure  **Support.** evidenced

**Holds when.**

- surveyed developer populations in industry code review

**Source quote.**

> 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

**From.** Wulf A. Kaal, *How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards* (2021), Lack of Feedback, page 10

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

**Verify.** sha256 of source PDF `6d77dbfb15ee86080bfde0b98089180cabafeb6defdf0f05eaaeb3cb99871e89` at https://raw.githubusercontent.com/wulfkaal/Academic-Papers/main/papers/pdf/Kaal%20-%202021%20-%20How%20DAOs%20Optimize%20Open-Source%20Code%20Reviews%20and%20Create%20Open-Source%20Standards.pdf

**Failure mode.** untimely or unhelpful feedback  (family: collective-action-and-coordination-failure)

**Topics.** institutional-design

**Keywords.** feedback-latency, review-quality, human-human-issues, failure-mode

**Canonical form.** This markdown file is the canonical hashed representation of the claim. Its sha256 is the content hash used for attestation.