how it works
Four steps, in order. Stop is always in reach.
- 1
build
Pick your device and snap when and do blocks. When the blocks cannot say it, take the code and write it yourself.
- 2
try it
The simulator runs what you built, line by line, before anything touches hardware.
- 3
ship it
Pick one of your devices. The program goes to it and turns on.
- 4
running
See what is on, and where. Turn one off, or stop everything at once.
player two
You make the call. Claude explains the why.
Player two sits beside the bench, not in front of it. It names the concept, points at the block, and says why a program breaks. Then it builds what you decide. No flattery, and no doing it for you.
youwhy did the light stay on?
player twoyour loop never turns it off, so the fill runs every pass. Add an else that clears it, or a second when.