> ## Documentation Index
> Fetch the complete documentation index at: https://meta.niceshare.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Cunningham's Law

> Cunningham's Law says people often correct a wrong answer faster than they answer a plain question. Learn origins, limits, and ethical use.

<Info>
  **Category**: Laws<br />
  **Type**: Online interaction heuristic (named aphorism)<br />
  **Origin**: Named after Ward Cunningham; popularized as an internet-culture principle<br />
  **Also known as**: McGeady’s formulation of Cunningham’s advice (informal)
</Info>

<Note>
  **Quick Answer** — Cunningham’s Law is the observation that **the fastest way to get a correct answer online is sometimes to post a wrong one**, because people are strongly motivated to correct errors. It is **not** an endorsement of dishonesty: it describes incentive structure in crowds, forums, and workplaces. Use it to design better questions, feedback channels, and review systems—not to manipulate people.
</Note>

## What is Cunningham's Law?

**Cunningham’s Law** names a recurring pattern in public, networked conversation: **corrections can arrive faster than helpful answers to neutral questions**, partly because error triggers status, identity, and clarity motives that a plain question may not. The idea is used in software communities, moderation theory, and teaching—always alongside ethics, because weaponized wrongness wastes trust.

> Corrections seek an audience; questions seek a volunteer.

It sits near [Brandolini’s Law](/laws/brandolinis-law) (refutation can cost more than fabrication—different axis) and [bikeshedding](/laws/bikeshedding) (easy topics attract disproportionate energy). Unlike [Hanlon’s Razor](/laws/hanlons-razor), it does not explain motives—only **response dynamics**.

### Cunningham's Law in 3 Depths

* **Beginner**: Notice when a slightly off detail draws instant fixes, while a vague question lingers unanswered.
* **Practitioner**: In reviews and RFCs, offer a **straw proposal** you are willing to revise—invite concrete corrections without pretending certainty.
* **Advanced**: Shape systems—templates, pair review, “most likely wrong” drafts—that harness correction energy without rewarding disinformation.

## Origin

The maxim is widely stated as: *the best way to get the right answer on the internet is not to ask a question; it’s to post the wrong answer.* It is **named after Ward Cunningham**, creator of the wiki concept. **Steven McGeady**, a former colleague, is commonly credited with **naming** “Cunningham’s Law” and recounting early-1980s advice about Usenet-style forums; the formulation later spread through tech culture and general internet discussion. **Cunningham himself has distanced himself** from some popular phrasings, treating them as error-prone memes—so treat the law as a **social heuristic**, not a personal quote engraved in stone.

## Key Points

Treat the law as a description of incentives, not a license to mislead.

<Steps>
  <Step title="Correction is socially salient">
    Errors threaten shared reality; fixing them can feel urgent and rewarding compared with writing an original answer from scratch.
  </Step>

  <Step title="Questions vary in cost to answer">
    Good answers may require research, tools, or responsibility; a wrong claim can be debunked from memory in one paragraph.
  </Step>

  <Step title="Ethics dominate tactics">
    Deliberately spreading false claims to farm corrections corrodes trust and can harm bystanders—especially in health, safety, and politics.
  </Step>

  <Step title="Design beats provocation">
    Pair programming, draft PRs, and labeled “hypothesis” documents capture the same fast feedback without pretending facts.
  </Step>
</Steps>

## Applications

Use the pattern to elicit expertise without exploiting readers.

<CardGroup cols={2}>
  <Card title="Engineering & product" icon="code">
    Share a minimal repro plus a **wrong guess** labeled as such to pull specific critiques faster than “thoughts?”
  </Card>

  <Card title="Education" icon="chalkboard-user">
    Use structured mistakes in exercises where the class knows the format—never surprise-stunt learners with disinformation.
  </Card>

  <Card title="Community moderation" icon="users">
    Pin clear “how to report errors” paths so corrections land as data, not pile-ons.
  </Card>

  <Card title="Research & writing" icon="book">
    Circulate a **deliberately incomplete** outline to surface citations people care about—distinct from fabricating results.
  </Card>
</CardGroup>

## Case Study

The law’s modern visibility tracks **named articulation in public writing** rather than a laboratory measurement. Reporting and community sources credit **Steven McGeady** with popularizing the eponymous label in connection with Cunningham, including discussion in a **2010** *New York Times* “Schott’s Vocab” blog context—an externally datable milestone for when the **name** entered wider discourse. That timeline matters: the underlying behavior (people correcting mistakes) is ancient, but **searchable documentation** of the branded principle clusters in the early 2010s, alongside growth of Stack Overflow–style venues where fast correction is a reputation currency.

## Boundaries and Failure Modes

**Boundary 1: Good-faith questions still work**\
Experts often answer clear, respectful questions quickly—especially in niche communities with shared norms.

**Boundary 2: Corrections can be wrong too**\
Pile-ons amplify confident mistakes; popularity is not accuracy.

**Common misuse**: Posting **knowingly false** claims to “win” engagement—this trains audiences to distrust you and can cause real harm.

## Common Misconceptions

Clarify what the law is not.

<AccordionGroup>
  <Accordion title="Misconception: Cunningham endorses lying">
    **Reality**: The useful core is incentive design; ethical practice avoids deceptive statements and labels uncertainties.
  </Accordion>

  <Accordion title="Misconception: It always beats asking">
    **Reality**: Many contexts reward well-framed questions; the law describes frequency, not universality.
  </Accordion>

  <Accordion title="Misconception: More controversy means more truth">
    **Reality**: Heat can reflect identity conflict, not epistemic quality—pair engagement with verification.
  </Accordion>
</AccordionGroup>

## Related Concepts

Link these when reasoning about online knowledge production.

<CardGroup cols={3}>
  <Card title="Brandolini's Law" icon="scale-unbalanced" href="/laws/brandolinis-law">
    Refuting nonsense can cost far more than producing it—pair incentives carefully.
  </Card>

  <Card title="Sturgeon's Law" icon="filter" href="/laws/sturgeons-law">
    Most content is low quality—corrections must be triaged, not infinite.
  </Card>

  <Card title="Bikeshedding" icon="paint-roller" href="/laws/bikeshedding">
    Trivial issues attract outsized discussion—watch what energy follows errors.
  </Card>
</CardGroup>

## One-Line Takeaway

<Tip>
  Harvest fast feedback with labeled drafts and crisp questions—never substitute manipulation for inquiry.
</Tip>
