Cost and caching
Why a 12-turn chat bills 43,800 input tokens, what prompt caching actually saves, and how one timestamp in the prompt quietly kills the cache.
A 4-hour hands-on session for engineers building with LLMs. You run five small AI systems, watch each one fail, and write the fix.
Each lab hands you a working system with one file left to write. The tests tell you when it works. The experiment after it shows you why it matters in production.
Why a 12-turn chat bills 43,800 input tokens, what prompt caching actually saves, and how one timestamp in the prompt quietly kills the cache.
A role filter applied after search starves the results and the bot says "no policy found". You move the filter inside search, then measure recall before and after a reranker.
Why 95% to 97% on 100 test items is noise, how many items you need before a change is real, and how one critical regression should block a prompt that scores "better".
A compromised model tries to move ₹38,000. You write the policy code that stops it without reading a word of the prompt.
Four context tiers under one token budget. A running summary acts on a customer's stale address, and you decide what should survive into the next session.
RULE: you write the fix, the tests tell you it works
this workshop: no slides to watch, code to run
Message me on LinkedIn with your tier and online or Bangalore. The format follows demand. I'll send a payment link; your seat is held once it's paid.
₹5,000 · Bangalore Message me on LinkedInThe same labs, run for one team, with the examples pulled toward what you're actually building. Useful when a team is moving from an LLM demo to something customers depend on, and needs a shared picture of where cost, retrieval, evals and agent actions go wrong.
Tell me your team size and what you're building. I'll come back with a plan and a price.
Ask about a team session