The LED is not the impressive part.
The important part is the learner seeing this loop clearly:
change code β run β physical system responds
That first visible win turns abstract programming into embedded systems. What should we demonstrate next?
GPIO in plain English:
Input: the Pi notices something.
Code: your program decides.
Output: the Pi makes something happen.
Button β logic β LED.
That small loop is the beginning of a lot of embedded systems.
Did your Raspberry Pi become drawer decoration?
The problem usually is not motivation. It is the fragmented path between setup, code, wiring and a working result.
This month we are showing how FigLab connects guided lessons to real hardware. What stopped your first Pi project?