# kaal:claim:3995709-007

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

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

**Holds when.**

- reviewers confused by unfamiliar code
- peer trust within a team

**Source quote.**

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

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

**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.** blind approval  (family: smart-contract-bug-and-exploit)

**Topics.** institutional-design

**Keywords.** blind-approval, code-confusion, review-quality, failure-mode

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