bench
sign in
a standpoints workbench
Build a machine. Ship it.
Teach a sensor to notice. Wire it to an action. Watch it become real code — then ship it to a Wi-Fi device on your desk. You build it; player two explains the why.
01000010 01100101 01101110 01100011 01101000 — 10110 01101 11001 00110
the bench
Pick what happens, and when. See the code it becomes.
device
when
do
teenyview
how it works
Blocks on the left. The same program, as real code, on the right.
- rung 1 · 2blocks → automationDrag "when → do." It runs on the fleet, survives a reboot, and you can watch it.
- the crossingtake the codeWhen blocks can't say it, the CircuitPython becomes yours to edit. A one-way door, taught as one.
- rung 3on the metalReal programming, on a device you own. The destination, not a demo.
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, says why a build breaks — then builds what you decide. The respect is the work: no flattery, no doing it for you.
youwhy did the light stay on?
player twoyour loop has no "off" branch — the fill runs every pass. add an else that clears it, or a second when.
three in a minute
Real builds, real code. These run on the fleet.
the fleet