Accelerate Robotics with AI: The firmware writes itself
About Event
You studied control theory, kinematics, state machines. Then you lost an afternoon to a toolchain because the driver was wrong and the cable only carried power.
The distance between knowing how a system should behave and getting a board to actually do it was never about intelligence. It was tooling. Tooling just changed.
What we're building
Two hours, one board, one cable. By the end yours is broadcasting its own WiFi network. You connect your phone to it, open a page the board itself is serving, and drive something with your thumbs. No internet, no cloud, no account, no company in the middle. A network that exists because you made it exist.
That's the artifact. It isn't the point.
The point is how we get there. I will not be writing most of the code, and neither will you. We'll be directing it, reading it back, catching where it's confidently wrong, and deciding what to build next. That last part is the only part that doesn't automate, and it happens to be the part you already spent years training for.
Why this room specifically
A curriculum is designed over months and lives for years. A model that writes working embedded C ships in weeks. That mismatch is nobody's failure, it's just arithmetic, and it means the highest leverage move available to an engineering faculty right now is putting the new tools in the hands of people who already have the fundamentals.
That's this room. You know what a PID loop is. You don't need me for that. What you may not have seen is how far the distance from idea to running prototype has collapsed, and what that does to the list of projects worth attempting.
The format
Not a lecture. Collaborative discovery, same as every AI Whisperers session. I'll have a board on camera doing exactly what yours is doing. You bring an actual question about something you want to build, and we aim the tools at it live and find out together where they hold and where they break.