By Amuchan | Developer Experience Team
There’s a moment in every major release cycle where the product manager says, “Let’s run a Kano workshop before we finalize v10.”
And every developer feels a small shiver. Not because Kano is bad—in fact, it’s brilliant—but because it usually means we have to kill our darlings. For v10, we didn’t just run a workshop. We rebuilt the workshop. amuchan developer v10 kano workshop work
Here’s how the Kano model shaped the work for Amuchan Developer v10, what we cut, what we doubled down on, and why the final build actually works.
Unlike standard CI/CD pipelines that push to GitHub or GitLab, Kano workshops produce what locals call "sneakernet builds." Amuchan v10 exports a portable binary that can be transferred via USB or Bluetooth to a staging server. This binary includes a manifest of all dependencies, ensuring the production environment (often a Raspberry Pi or NUC) runs identically. By Amuchan | Developer Experience Team There’s a
Open the Kano terminal (Ctrl+Alt+T) and execute:
wget https://repo.amuchan.dev/v10/kano-amd64.deb
sudo dpkg -i kano-amd64.deb
amuchan --version
Expected output: Amuchan Developer v10.0.2 (build 4421) Expected output: Amuchan Developer v10
| Tool | Purpose |
|------|---------|
| kano-gpio | Python/C bindings for GPIO with interrupt support. |
| fb-kit | Direct framebuffer drawing (bypassing X11). |
| am-sensor | Unified API for Kano’s accelerometer, light sensor, and temperature sensor. |
| v10-bootstrapper | Script to apply persistence mods after reboot. |