Why blinking an LED is the most important program you'll write

The first time a microcontroller blinks an LED, something profound has happened. A quartz crystal — vibrating sixteen million times a second — has driven a digital clock distributor, which has driven an instruction pipeline, which has decoded a byte, which has flipped a single bit in a register, which has switched a transistor, which has sourced enough current to bias a semiconductor diode forward. And then, six instructions later, it has done the opposite.

People dismiss blink.ino as the trivial "hello world" of hardware. It isn't. printf("hello\n") is a function call into a library that hands the bytes to an operating system, which hands them to a kernel, which hands them to a driver, which hands them to a terminal emulator. There are millions of lines of code under that one statement. Blink reaches the metal directly.

Look at the sketch:

void setup() {
  pinMode(13, OUTPUT);
}

void loop() {
  digitalWrite(13, HIGH);
  delay(500);
  digitalWrite(13, LOW);
  delay(500);
}

pinMode(13, OUTPUT) sets one bit in the Data Direction Register B (DDRB) — bit 5, because pin 13 on the Uno maps to PB5. That bit configures a tiny transistor in the chip to either drive the pin's voltage or leave it floating. One bit. One transistor. Real, physical metal.

digitalWrite(13, HIGH) sets bit 5 of the Port B output register (PORTB). The transistor switches; the pin rises to 5 volts. Through a 220-ohm resistor, that drives about 14 milliamperes through the LED's silicon junction, where electrons recombine with holes and release the energy as photons. You can see the photons.

delay(500) spins the CPU for eight million clock cycles, doing useful arithmetic that adds up to nothing — just waiting. Half a second later, digitalWrite(13, LOW) clears the bit, the pin sinks, the current stops, the diode goes dark. Then the loop repeats.

If you understand what each of those lines is doing, you understand a microcontroller. Every more sophisticated program you'll ever write — read a sensor, drive a motor, talk over WiFi, sweep a servo — is just more of the same: registers, bits, pins, voltages. Blink is not the small thing before the big thing. Blink is the thing.