If printing “Hello, World” is the traditional first step in learning a programming language, then making an LED blink is its equivalent in the world of hardware. When you wire up a new microcontroller board, the first thing you usually do is load a tiny program that turns a single light-emitting diode on, waits, turns it off, waits, and repeats forever. The reward is small and unmistakable: a blinking light that proves your toolchain works, your board is alive, and your code is actually running on real silicon.
The Arduino project turned this rite of passage into something a beginner could do in minutes. Arduino’s official documentation ships “Blink” as a built-in example, the canonical starting point for anyone new to the platform. It demonstrates the two-function shape of every Arduino sketch: a setup() function that runs once when the board powers up, and a loop() function that the board runs over and over for as long as it has power.
The logic is deliberately minimal. In setup(), the sketch calls pinMode to configure the board’s built-in LED pin as an output. In loop(), it calls digitalWrite to drive that pin HIGH, turning the LED on, then delay to pause, then digitalWrite to drive the pin LOW, turning it off, then delay again. Arduino’s language reference describes digitalWrite as the call that writes a HIGH or a LOW value to a digital pin that has been set to OUTPUT. Those few lines contain almost everything a newcomer needs to grasp about embedded programming: pins, direction, digital state, and timing.
What makes Blink powerful as a teaching tool is how much it hides while still being honest. The beginner does not need to understand clock registers, interrupt vectors, or the chip’s datasheet to see the light blink. Yet the program is real firmware running on a real microcontroller, not a simulation, so the success is genuine. From there it is a short hop to reading a sensor, driving a motor, or sending data, and many embedded careers began with exactly this first flashing LED.
Blink endures because it answers the most important early question in any hardware project: is this thing working at all? A blinking LED is the simplest possible yes. It is the moment a pile of components becomes a computer that is doing what you told it to, and that small, repeating light has welcomed an entire generation into embedded computing.