Imperative programming · Literal execution

Robot Dance

Write dance moves in order. Literal execution, made visible.

The robot does exactly what you tell it, in exactly the order you wrote it. No interpretation, no helpful guesses. Off-by-one and out-of-order sequences are the dominant class of beginner bugs in every imperative language — because programs don't 'mean what you meant'; they do what you wrote.

Robot Dance Choreographer

Pick moves to build a dance routine, then hit Play!

🤖

What’s happening under the hood

›Imperative programming: a sequence of statements executed top to bottom. C, Python, JavaScript, Java all share this core model.
›Each move is a function call with no return value — just a side effect on the robot's state. Mutating shared state is also the source of most concurrency bugs in real systems.
›The opposite paradigm — declarative — describes what you want rather than how to do it. SQL, HTML, regex, and Datalog are declarative; they let the engine pick the procedure.

Dig deeper

Phase 1 · Control Flow

The concept you just explored is taught with full depth in the formal DURA curriculum.