See all tags.
Day goal: participants leave Day 2 able to architect, implement, and deploy AI-native features — streaming, tool-calling agents, RAG pipelines, and MCP servers — all in idiomatic, production-quality C#.
Summary — what this page covers The Day 2 pre-flight. The key difference from Day 1: this day runs on the Anthropic API (pay-as-you-go), which is separate from a Pro/Max subscription — an API key is required.
Summary — what this page covers A map of what Day 2 adds to the BookTracker solution from Day 1. Each section drops new files into the same codebase attendees already understand.
9:00 – 10:30 AM · 90 min — 45 min lecture/demo + 45 min lab
Duration: 45 min · Deliverable: working /api/chat with history and prompt caching — committed
/api/chat
10:45 AM – 12:00 PM · 75 min — 40 min lecture/demo + 35 min lab
Duration: 35 min · Deliverable: streaming endpoint + multi-tool agent — committed
1:00 – 2:15 PM · 75 min — 35 min lecture/demo + 40 min lab
Duration: 40 min · Deliverable: working /api/recommend with grounded responses — committed
/api/recommend
2:15 – 3:15 PM · 60 min — 30 min lecture/demo + 30 min lab
Duration: 30 min · Deliverable: BookTracker.Mcp with 3+ tools connected to Claude Code — committed
BookTracker.Mcp
3:30 – 4:15 PM · 45 min — 20 min lecture/demo + 25 min lab
Duration: 25 min · Deliverable: AI-generated tests passing + GitHub Actions AI review + release-notes job, committed
4:15 – 5:00 PM · 45 min — Discussion + Q&A
Free-first: default to free/local where possible; pay only where it's genuinely required.
Summary — what this page covers Quick answers to the recurring Day 2 questions. Carry over the existing Day 2 FAQ and keep answers to a few sentences. The API-vs-subscription confusion is the #1 item — lead with it.