This repository contains all notebooks and supporting files for Partner Basecamp sessions. Materials are organized by day and session in the order they run.
- Click the green Code button at the top right of this page.
- Select Download ZIP.
- Unzip the file on your computer — you'll get a
Basecamp-Exercises-mainfolder with everything inside.
git clone https://github.com/victorsteeb/Basecamp-Exercises.git| Folder | Session | Type |
|---|---|---|
day1/01_claude-code-workshop |
Claude Code Workshop | Offline guide |
day1/02_developer-platform |
Developer Platform | Build-Along |
day1/03_prompt-rescue |
Prompt Rescue | Build-Along |
day1/04_diagnosing-ai-problems |
Diagnosing AI Problems | Session materials |
| Folder | Session | Type |
|---|---|---|
day2/01_evals |
Evals | Build-Along |
day2/02_inference-optimization |
Inference Optimization | Build-Along |
Each folder has its own README with the exercise description and step-by-step run instructions.
You'll need an Anthropic API key for all build-along sessions — and you don't need a terminal to set it. Run the notebook's setup cell once: it creates a gitignored .env file. Open it, paste your key after ANTHROPIC_API_KEY=, save, and re-run — a green "✓ API key verified" banner confirms you're connected. The key lives in .env, never in a notebook cell (notebooks have a way of ending up in client repos), it survives kernel restarts, and a single .env at the repo root serves every exercise.
Prefer to set it once for everything? That works too:
export ANTHROPIC_API_KEY=your_key_here # your shell, the VS Code terminal, or a local .envThese build-alongs are meant to run in your own tooling, not a browser scratchpad — and never by pasting code out of a chat window:
- VS Code / Cursor — open the folder, then the notebook (Jupyter extension) or run the
.pyin the terminal. - Claude Code (CLI) —
claudeinside the repo: run the.py, or work the exercise with Claude Code as your pair. - Claude Desktop — keep it open alongside as your AI pair for concepts and debugging.
Each session's README has the exact steps.
The notebooks install what they need on first run and survive locked-down corporate Pythons
(the externally-managed-environment / PEP 668 error, no-admin machines, proxies). If you hit
a wall, SETUP.md is the one-page fix — it covers the venv path, the VS Code
"wrong kernel" trap, and corporate-proxy installs. For a pinned environment up front:
python3 -m venv .venv && source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -r requirements.txt