Feynman’s Razor

What counts as “Feynman’s Razor”?

• Some argue it doesn’t meet the definition of a philosophical razor (a quick rule for eliminating explanations), calling it more a “don’t dumb it down” guideline.
• Others say it is a razor: it filters explanations by whether an expert can still recognize what is being talked about.
• There is meta‑discussion about what even qualifies as a “razor” and whether we need a “metarazor” for that.

Expertise vs ability to explain

• One view: Feynman wrongly equated expertise with teaching skill; many experts are poor explainers, and some non‑experts can teach well.
• Counter‑view: inability to explain often reveals shallow understanding; explaining forces deeper mastery.
• Feynman’s own lectures are seen as powerful for people who already know physics, but often ineffective as first exposure.

Error messages and user communication

• The cited “message doesn’t exist but you can copy it” example is widely criticized as confusing.
• Proposed alternatives: specify “on the server vs on your device/cache,” and focus on clear actions (“save a copy,” “discard”).
• Some favor two layers: a simple actionable message plus an optional “advanced explanation.”
• Debate over how much cause detail users need; some say only next steps matter, others insist cause and action both matter.

Dumbing down vs accessibility

• Many see a trend toward over‑simplification (UI copy, journalism, search results) that treats users as unintelligent and blocks learning.
• Others note that business incentives (engagement, fewer support tickets) often reward this behavior.
• A contrasting UX principle: users are smart but busy; interfaces should respect their intelligence and their time.

Analogies, intuition, and technical depth

• Mixed feelings about Feynman’s popular analogies (e.g., “little arrows” in QED):
  • Pro: powerful intuition and geometric feel without algebra.
  • Con: can confuse those capable of learning the math but not yet taught it; risks “phibs” (oversimplifications that mislead).
• Some advocate combining precise terms with brief explanations, and using code/numerical examples to ground intuition.

Respectful technical writing and settings

• Praised examples include tools that explain concepts, risks, and options in plain but complete language (e.g., old utilities like disk doctors).
• Cryptic prompts (“Mode 5/7? [Y]”) and context‑free confirmations (“Are you sure? [N]”) are condemned.
• Calls for more inline explanations/tooltips in settings, and for writing that leaves readers more knowledgeable rather than merely placated.