NastępnyNastępny poradnik
Simpson's Paradox
Podstawy
PODSTAWOWY PRZEWODNIK
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.
Na tej stronie3 minuty czytania
Przegląd
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.
Głębokie nurkowanie
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.
Wpływ strategiczny
Jaśniejsze decyzje
Pomaga oddzielić jasne twierdzenia techniczne od języka marketingowego.
Koszt i budżet
Możesz zadawać pytania dotyczące lepszego wdrożenia, zanim wydasz pieniądze lub czas.
Zespół i przepływ pracy
Zespoły charakteryzujące się wspólnym zrozumieniem podejmują lepsze decyzje dotyczące produktów, zasad i uczenia się.
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.
Implementacja w świecie rzeczywistym
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.
Zagrożenia i poręcze
Różne zespoły mogą odmiennie używać tego samego terminu, dlatego należy wcześniej zdefiniować zakres.
Testy porównawcze mogą wyglądać dobrze, podczas gdy wydajność w świecie rzeczywistym jest nierówna.
Ignorowanie planów dotyczących jakości danych i oceny często skutkuje kruchymi wynikami.
Plan wdrożenia
Zacznij od jasnej definicji potrzebnego wyniku.
Przed testowaniem wybierz jedną metrykę sukcesu i jeden warunek niepowodzenia.
Przeprowadź mały pilotaż z reprezentatywnymi danymi, a nie dopracowanym zestawem demonstracyjnym.
Document where Moravec's Paradox helps and where simpler methods are better.
Odkrywaj dalej
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.
Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation
Często zadawane pytania
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.
Ucz się dalej
Powiązane przewodniki
Wybrano więcej przewodników na ten temat