Finger Speed Is the Real Interface Contract

·https://aresluna.org/show-your-hands-honor/
articledesigninteraction-designhciuilatencymotor-memoryoperator-uxpiagent-ui

maps directly to joelclaw operator UX: agent work can be slow, but command entry, streaming feedback, focus, and cancellation need finger-speed behavior

Marcin Wichary built a 7,700-word Aresluna interactive essay about a simple, brutal constraint: fingers don’t wait for software. Typists beat old theoretical speed limits because their fingers overlap in time, with one finger already moving while another finishes. Good interfaces have to respect that same weird human superpower.

The clever bit is that Show your hands honor for the strange power they bring you makes latency feel physical. Slow terminal echo, sticky buttons, bad search-as-you-type, over-loud loading states, dead zones, spring-loaded modes, Undo, Esc, Chrome tab behavior, iPhone scrolling, Gmail hovercards, and Notion selection all get judged by the same standard: does this cooperate with motor memory, or does it interrupt it?

For joelclaw, this is operator UI doctrine. Pi, cmux, the gateway, and agent loops can kick off work that takes seconds or minutes. Fine. But typing commands, keeping focus, streaming partial output, showing progress, and smashing an abort key should never feel like the backend is grabbing your fingers and saying “hold up, buddy.” Let the agent shit be slow in the background. Keep the interface fast under the hands.

Key Ideas

  • Wichary frames fast typing through overlapping: fingers begin future actions before earlier actions finish, so UI timing has to fit human motion instead of serial computer logic.
  • Local echo, buffering, debouncing, optimistic updates, and parallel UI handling are old answers to the same problem: feedback must arrive at finger speed even when real work is slower.
  • Loading states are not just truth-telling widgets; the essay argues their job is to make software feel fast, which means sometimes staying quiet, delaying display, streaming partial output, or pretending optimistically.
  • Motor memory turns shortcuts like ⌘Z, find/find-again, Finder space preview, and Esc into unconscious gestures. Breaking those gestures is not a minor papercut. It is the interface picking a fight with the user’s hands.
  • Fine interaction details like dead zones, press-vs-hold thresholds, spring-loading, modality switching, and “last modality wins” are not polish glitter. They are how software avoids punishing fast, messy, human movement.
  • The iPhone scrolling section is a useful benchmark: touch interaction felt supernatural because the system prioritized the finger path so hard that smooth scrolling could interrupt other work.

Links

← All discoveries