liveBook · Manning

Curse of Knowledge

As explained in Crack Any Codebase with AI

The Curse of Knowledge is a cognitive bias in which knowing how something works makes it difficult to imagine the perspective of someone who does not know it.

The Curse of Knowledge is the bias that makes implementation fluency obscure the user's perspective. An engineer sees database tables, API routes, and workers; a user may experience only relief from scheduling anxiety. section 5.1

One button, two realities

A developer may describe scheduling as checking whether two date ranges overlap. A sales manager experiences replacing nine emails, double-booking fears, and calendar coordination with one link. The implementation is a mechanism; the product is the pain it removes. section 5.1

Counter the bias by asking:

  • What user pain exists before the feature? section 5.6
  • Does the description explain why the product exists, rather than merely inventorying features? section 5.6
  • Could someone reproduce the product from one sentence? section 5.6

How Crack Any Codebase with AI covers it

How deep it goes
Defines the bias, contrasts engineer and user perspectives, and applies it to product descriptions and real products.
Examples
Uses scheduling coordination, Dropbox file syncing, Supabase infrastructure, and comparisons between code mechanisms and customer pain.
What it assumes
Assumes familiarity with implementation details while teaching the user perspective through concrete product contrasts.
What you can do after
Evaluate product intent by identifying user pain and testing whether a description explains a reproducible product.
How it connects
Connects user perspective with product intent, feature lists, implementation details, and counter-positioning.

This explainer was generated by Manning's knowledge graph from the text of Crack Any Codebase with AI. The section links point to the parts of the book it draws on.