Home › Foundations › Week 9
Week 9 of 12
Calling an LLM like an engineer, not a tourist
Call a real LLM API from Python, manage prompts and responses as structured data, secrets via env, log every call.
Why this resource? 60 second framing
Open the curated resource above and come back here when you have run it or watched it once. The coach is the right place to talk about what you saw.
What you ship by Sunday
Public repo summarize-it, a script taking a URL or text file, calling a real LLM API, returning a 5-bullet summary with source preserved, logging prompt+response+tokens to JSONL. .env never committed, .env.example committed.
The coach (Socratic, one hint per turn)
30 messages / dayThe coach gives you one hint per turn. Never the answer. Hinglish bilkul welcome hai. It cannot do arithmetic; run code yourself and paste the result.
Ask for a Socratic review of your artifact
Paste your README (or a draft of it). The coach will read it like an honest senior would, ask one question that surfaces the weakest link, and point at one thing to tighten. It will not rewrite it for you. Maximum 8000 characters.
Before you close the tab
Three short questions to answer in your own words, even just in your head. The point is to notice what you actually learned this week, not to perform learning back at the coach.
- What broke first when you tried this week artifact, and what did you do?
- Pick one line of code that confused you initially. What does it do?
- If you had to rebuild this from a blank file tomorrow, what would you start with?