How LLMs Work
Tokens, embeddings, attention and next-token prediction — the mechanics that explain almost every LLM behaviour.
- 4 lessons
- 1h 4m
- 3 simulations
Calling APIs, streaming, tool calling, caching, and keeping cost and latency under control in production.
A suggestion, never a lock — you can start here.
Every lesson's title and summary is public. The lessons themselves open once you own the track.
Every lesson in LLMs, Prompt Engineering & Context EngineeringOne endpoint, one request shape: messages, roles and parameters — then streaming so the user is not staring at a blank screen.
The model runs nothing: it asks, your code executes, and the result goes back. Understanding that division of labour is the whole of tool-calling safety.
An LLM bill is dominated by input tokens sent over and over. Prompt caching, a trimmed context, batching, and a model that is good enough — in that order.
The API will slow down and occasionally fail. An app that survives knows which errors to retry, waits with backoff and jitter, limits concurrency, and has a fallback.
Tokens, embeddings, attention and next-token prediction — the mechanics that explain almost every LLM behaviour.
Clear instructions, examples, step-by-step reasoning and structured output — proven techniques, no incantations.
What goes into the context window, where it comes from and in what order — the core skill of building LLM applications.
Eval sets, LLM-as-judge and regression tests for prompts — replacing "looks good to me" with a number.