Very hands-on
Two 3-hour studios a week. Studio A is a short talk (20 minutes at most) and a lab; Studio B is a workshop with practice, project time and help. You ship five projects.
See the projects
Build real software with AI, on a $0 budget. A hands-on University of Idaho course that takes people who have never coded to shipping a deployed web app by directing AI tools, and teaches the habits that make that software trustworthy. 3 credits · eight accelerated weeks · two 3-hour studios a week.
| Week | Title | You build |
|---|---|---|
| 0 | Pre-work | Accounts, privacy settings and a first AI-built page, before Studio 1 |
| 1 | Hello, Vibe Coding | A personal home page, live on the web, and your own AI-use rules |
| 2 | Prompting & Save Points | A browser game in one hour, with git save points |
| 3 | Spec First | Project 1 from your own one-page spec |
| 4 | Read It, Debug It, Own It | The Debug Clinic (AI off), your first automated test, Project 1 final |
| 5 | APIs, Secrets & Servers | An AI-powered micro-app with a hidden API key |
| 6 | How Agents Work | "Be the Agent"; your capstone's first agent-built feature and pull request |
| 7 | Security, Data & Review | The RLS Attack Lab; a database for your capstone |
| 8 | Ship It | Capstone polish and the Project Fair |
| # | Step | What you do |
|---|---|---|
| 1 | Describe | Goal, context, constraints, "done when". Write the check first |
| 2 | Plan | Ask for a plan, and edit it before any code is written |
| 3 | Step | One small change at a time |
| 4 | Test | Run your check, the normal case and an edge case |
| 5 | Read | Read the diff, and write a short teach-back of what changed and why |
| 6 | Commit | A git save point with a clear message |
If two fixes in a row fail, stop, start a fresh chat and rewrite the prompt: the two-strikes rule. Printable card.
Tools change often
Every price, limit and model name lives on one page, Tools, which carries the date it was last checked.