JOVANA
Library Glossary Getting Started Three Levels Fields How it works Mission
Join the mission
All guides

Why the Easy Things Are Hard

Robots crush chess but fumble a shoelace, and code that's flawless in simulation flails in the real world. Two famous gaps explain why — and how the field is closing them.

Moravec's Paradox: the upside-down difficulty scale

Ask a person to multiply 4,827 by 391 in their head and they will sweat. Ask them to pick up a coffee cup, walk across a cluttered room, and recognize their friend's face, and they do it without a thought. For a robot, the difficulty is exactly reversed: the arithmetic is trivial, while the cup, the walk, and the face are brutally hard. This inversion is called Moravec's Paradox.

Why? The roboticist Hans Moravec pointed to evolution. The skills that feel effortless to us — seeing, grasping, balancing, reading a room — are the oldest in our biology, polished by hundreds of millions of years of survival pressure. They run on vast, silent neural machinery that never reaches conscious awareness, which is exactly why they feel free. Abstract reasoning like algebra is a thin, recent layer, only a few thousand years old, and it shows: it is slow and effortful precisely because it is new.

So the things we are proud of — chess, logic, calculation — are the easy ones to automate, because they are already written down as crisp rules. The things we never think about — feeling a sock's edge, catching ourselves when we slip — are the hard ones, because nobody ever wrote the rules; evolution baked them straight into our bodies.

The reality gap: when perfect code meets messy hardware

There is a second, sneakier gap. You write a controller, test it in a simulator where the robot walks flawlessly a thousand times in a row, then load the exact same code onto the real machine — and it stumbles on the first step. This painful surprise has a name: the reality gap.

The cause is simple but stubborn: a simulator is only a model, and no model captures the world perfectly. Real friction in the joints is never the tidy number you typed in. Contact — the instant a foot or a fingertip touches something — is notoriously hard to simulate, full of tiny slips and squishes. Sensors add their own grit; every reading carries a little noise and drift. Stack a hundred small mismatches and the carefully tuned controller drifts off the script.

Notice that Moravec's Paradox and the reality gap are two faces of the same coin. Both say: the physical world is richer and messier than any clean rule or model. Walking is hard for the same reason simulation leaks — contact, friction, and noise are everywhere, and they refuse to be fully written down.

Sixty years of chipping at the gaps

The history of robotics is, in large part, the story of teams chipping away at these two gaps. The first big move sidestepped them entirely.

  1. 1961 — Unimate. The first industrial robot, Unimate, went to work on a General Motors line, lifting hot die-castings. Its trick was to avoid the hard problems: bolt it down, hand it a fixed script, and remove all surprises. No vision, no balance, no messy contact — just the same precise motion, forever.
  2. 1970s–90s — sense, then plan, then act. As robots left the fixed cage, researchers built the sense–plan–act loop: read the world, compute a plan, move, repeat. It worked, but slowly — every step leaned on a model of the world, and the reality gap kept punishing the holes in those models.
  3. 2004–2015 — the DARPA leaps. The DARPA Challenges pushed cars across a desert and humanoids through a disaster course. They forced robots to cope with the unscripted real world — open terrain, debris, doors — and the field learned, painfully, how wide the reality gap really is.
  4. 2015–today — learning instead of scripting. Rather than hand-write every rule, robots now learn from data and from millions of simulated trials, then cross the gap with tricks like domain randomization. This is how a robot dog learns to scramble over rubble it has never seen, or a hand learns to flip a single object.

Each era did not erase the gaps; it narrowed them. Unimate avoided them, sense–plan–act confronted them, DARPA measured them, and learning-based methods are slowly closing them — especially for the once-impossible "easy" skills like rough-ground walking and reliable grasping.

The lesson: intelligence lives in the body

If both gaps come from the same place — the unwritten richness of the physical world — then the unifying lesson is also one idea: embodied intelligence. Real-world competence is not just a brain pushing commands to a dumb body. The body, the sensors, the contacts, even the springiness of the limbs all do part of the thinking. A clever hand makes grasping easier; compliant legs absorb a bad step before any controller even reacts.

This reframes the whole goal. The point is not to build a perfect mind and bolt it onto any body, but to co-design body and behavior so the physics works for you instead of against you. That is why so much of robotics is mechanical and physical, not just code — and why the rest of this ladder spends its time on joints, sensors, contact, and control rather than on abstract reasoning alone.