# kaal:claim:3995709-005

**Claim.** Proposed remedies for patch size, namely distributing the workload across a broader set of reviewers and providing better transparency on developer review queues, have not solved the problem; patch size remains an issue affecting the quality, speed, and effectiveness of modern code review.

**Type.** failure  **Support.** argued

**Holds when.**

- existing remedies deployed within legacy review processes

**Source quote.**

> However, despite the proposed solutions, many commentators recognize that patch size remains to be an issue for modern code review affecting the quality, speed, and effectiveness of the process.

**From.** Wulf A. Kaal, *How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards* (2021), Patch Size, page 7

**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.** ineffective patch size remedies  (family: governance-participation-collapse)

**Topics.** open-source-and-code

**Keywords.** patch-size, remedy-failure, code-review, failure-mode

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