The Model Call
WritingOne API request that takes eight seconds, streams, costs money, and can fail halfway. Timeouts, retries, queues, and state.
Everything between a model and a shipped product.
What a language model is, and what has to exist around it.
One API request that takes eight seconds, streams, costs money, and can fail halfway. Timeouts, retries, queues, and state.
How models are trained, what they can take in, and why the same input gives different answers.
How to get the output you want, and how to know when you have it.
Writing the instruction: what to say, what to show, what to ask for.
Everything else in the window, and how to spend a limited budget.
Measuring quality so you can tell whether a change helped.
Giving the model access to your code, your data, and its own past.
Getting back objects your code can act on, and calls it can run.
Images, audio, and documents in. Images and speech out.
Finding the right information and putting it in front of the model.
What persists between calls, and where it actually lives.
How the pieces fit together, what happens when they break, and how you see it.
Splitting work across calls you control, and handling the ones that go wrong.
Interfaces for output that might be wrong: confirmation, editing, undo.
Tracing requests in production, versioning prompts, rolling out changes.
Unreliable output, hostile input, and data you're responsible for.
Checking input and output before either reaches somewhere it shouldn't — and the attacks that arrive as text.
Who sees user data, where it goes, how long it stays.
What each request costs, how fast it feels, and which model handles it.
Where the money goes per request, and how caching changes it.
Time to first token, perceived speed, and what to show while waiting.
Choosing a model per request, with fallbacks when one fails.
The expensive options, and deciding what you actually need.
Handing the loop to the model instead of driving it yourself, and the cost of that decision.
Fine-tuning, LoRA, distillation, and why prompting is usually enough.
Nothing here is published yet. Parts I–III are being written first — the rest of the map is public so you can see where it goes. The guides I have already shipped live on the Tech Stack.