Grunnleggende GUIDE

Moravec's Paradox

Moravec’s paradox describes the surprising contrast between some formal tasks computers handle well and everyday perception or movement that can be difficult to engineer.

  • 3 minutters lesing
  • Sist oppdatert
På denne siden3 minutters lesing
  1. Oversikt
  2. Dypdykk
  3. Strategisk innvirkning
  4. The Future of Moravec's Paradox
  5. Real-World Implementering
  6. Risikoer og rekkverk
  7. Veikart for implementering
  8. Fortsett å utforske
  9. Ofte stilte spørsmål

Oversikt

It is a historical observation about uneven capabilities, not a rule that all reasoning is easy for machines or all physical work will remain beyond them.

Dypdykk

People can find a task effortless without being able to explain all the processes that make it possible. Recognizing a familiar object, reaching around an obstacle or adjusting a grip involves perception, coordination and feedback. Calling these activities simple describes an experience, not necessarily a small engineering problem. The contrast associated with Hans Moravec arose in work on AI and robotics. His historical writing compares progress in calculation and narrow symbolic tasks with the difficulty of getting robots to perceive and navigate everyday surroundings. He offered an evolutionary perspective: perception and movement draw on deeply developed biological capabilities, whereas formal calculation is a comparatively learned activity. That perspective helps explain the intuition; it is not a measured conversion between a brain and a computer. Consider a hypothetical board-game assistant. If it receives an exact symbolic position, it can focus on selecting a move. A physical robot facing the board must also identify pieces, estimate locations, plan motion, handle uncertainty and check what happened after acting. Success on the symbolic part does not establish success on the complete physical task. Use the paradox to ask better evaluation questions, not to freeze the state of technology. Sensors, algorithms, data and hardware can change which tasks are feasible. Formal reasoning also includes difficult problems, and some physical tasks can be highly constrained. Break an application into sensing, representation, planning, control and recovery, then test the actual combination under relevant conditions. A short demonstration on a prepared surface says less about reliable operation in a changing environment than repeated, varied trials with clearly recorded failures.

Strategisk innvirkning

Tydeligere avgjørelser

Det hjelper deg å skille klare tekniske påstander fra markedsføringsspråk.

Kostnad og budsjett

Du kan stille bedre implementeringsspørsmål før du bruker penger eller tid.

Team og arbeidsflyt

Team med delt forståelse tar bedre produkt-, policy- og læringsbeslutninger.

The Future of Moravec's Paradox

Robotics progress may change the boundary between tasks that are practical and tasks that remain difficult, without making capability uniform across domains. A system could improve at grasping familiar objects while still struggling with unexpected materials or recovery after a mistake. Future claims should therefore be evaluated through representative attempts and complete outcomes, including failures. The useful legacy of Moravec’s paradox is a warning against judging machine difficulty from human intuition alone. It encourages careful task definitions and evidence about the whole system rather than a permanent forecast about what robots cannot do.

Real-World Implementering

A hypothetical system solves a board-game position represented as symbols, but a robot must first locate the real board and pieces before it can act.

A warehouse team evaluates reaching, grasping and collision avoidance separately rather than inferring them from a chatbot’s explanation of the task.

An engineer compares a robot demonstration on a clear table with tests involving clutter, changing light and objects that move.

A student separates a claim about human familiarity from a measurement of computational or engineering difficulty.

Risikoer og rekkverk

  • Ulike team kan bruke samme begrep forskjellig, så definer omfang tidlig.

  • Benchmarks kan se sterke ut mens ytelsen i den virkelige verden er ujevn.

  • Å ignorere datakvalitet og evalueringsplaner skaper ofte skjøre resultater.

Veikart for implementering

  1. Start med en klarspråklig definisjon av resultatet du trenger.

  2. Velg én suksessberegning og én feilbetingelse før testing.

  3. Kjør en liten pilot med representative data, ikke et polert demosett.

  4. Document where Moravec's Paradox helps and where simpler methods are better.

Fortsett å utforske

Free newsletter

Get the daily AI briefing

Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.

One email each weekday. Unsubscribe in one click. We never sell or share your address.

Test yourself

Take the Moravec's Paradox quiz

Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.

Start quiz

Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation

Ofte stilte spørsmål

What is Moravec's Paradox?

Moravec’s paradox describes the surprising contrast between some formal tasks computers handle well and everyday perception or movement that can be difficult to engineer. It is a historical observation about uneven capabilities, not a rule that all reasoning is easy for machines or all physical work will remain beyond them.

A task feels effortless to a person. What does Moravec’s paradox caution against assuming?

Human familiarity does not measure the computational or engineering work required.

A game program receives a correct symbolic board position. What extra challenge appears when a robot faces the physical board?

The robot must identify pieces and locations, plan and execute motion, and verify the result.

How should Moravec’s evolutionary explanation be treated?

The guide presents the evolutionary account as an explanatory perspective rather than a numerical conversion or fixed law.

A robot succeeds once on an uncluttered table. What is needed to assess reliable use in a changing workspace?

A prepared demonstration does not establish performance under varied conditions.

Why separate recognition failures from grasping failures?

Stage-level diagnosis helps locate errors, but the complete outcome still matters.