# Patch size

`kaal:entity:patch-size`

**Status.** derived

This node is assembled mechanically from the 3 claims that carry the concept tag `patch-size`. 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

3 claims across 1 works, 2021 to 2021.

**2021**

- [3995709-002](https://wulfkaal.github.io/claims/3995709-002) [mechanism/evidenced] -- The benefit of a code review is negatively correlated with the size of the code under review: the larger the number of files in a single review, the lower the rate of beneficial feedback from reviewers.
  > Therefore, the benefit of attaining a code review is negatively correlated with the size of the code under review. In particular, the larger the amount of files in a single review, the lower the rate of beneficial feedback from the reviewers.
  Wulf A. Kaal, How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards (2021). SSRN: https://ssrn.com/abstract=3995709
- [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-005](https://wulfkaal.github.io/claims/3995709-005) [failure/argued] *(failure mode)* -- 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.
  > 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.
  Wulf A. Kaal, How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards (2021). SSRN: https://ssrn.com/abstract=3995709

## 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/patch-size.md | sha256sum

**Canonical form.** This markdown file is the canonical hashed representation of this entity node. Its sha256 is the content hash.