Your first AI script
Your own API key, your own code, calling a frontier model — before the first session ends.
Six sessions, six things you ship. One weekend or six evenings. Any laptop. ₹0.
Every session ends with working code in your hands — not notes about someone else's code.
Your own API key, your own code, calling a frontier model — before the first session ends.
A tester that measures whether AI answers are right — like an engineer, not a fan.
Upload a photo, interrogate it. AI that reads documents, receipts and handwriting.
An AI that answers from your material — RAG, the pattern behind most real AI products.
AI that calls tools your code controls — and the judgment to know when not to build an agent.
Attack each other's apps, patch the holes, then demo a real product to the room.
Two widgets lifted straight from the decks. This is how the course teaches: you play first, the explanation lands second.
Same prompt, same model, different answers. That is not a mood. The model never simply takes the best word: it rolls a weighted die. Temperature reshapes the dice before the roll.
You ask in your own words. Your notes were written in someone else’s. Ctrl-F needs the exact word and comes back empty. Embeddings turn every line into coordinates, so the closest meaning still wins.
A real 164k-parameter model trained on the 1,330 kurals, running in your browser — tokens, embeddings, attention, prediction, fine-tuning, RLHF.
Each session hands its verb to the next. Pick a node to open a session, see every slide, and tick it off when you've shipped its artifact — progress stays in this browser.
Next-token prediction, tokens, embeddings, attention, training vs inference — the whole engine, every idea a live demo, including a neural network you watch think.
Prompt engineering that works, why polished prompts still lie beautifully, and how engineers measure quality with numbers instead of vibes.
Vision that reads documents, diffusion that paints from static, voices cloned in seconds — and why it's all the same loop.
Embeddings, semantic search, chunking, and RAG end to end — the single most useful pattern in applied AI.
Tool use, the agent loop, MCP, why workflows beat agents most days — plus a frontier model running on a bare laptop.
Live prompt-injection attacks, defense in depth, what production actually costs — then you demo your capstone.
colab notebooks for all six labs ship in the labs/ folder of the course repo · progress is saved only in this browser — nothing leaves your machine · ←/→ moves between sessions
Half the course is laptops-open lab time. The talks exist to make the labs land — not the other way around.
Next-token prediction, prompting and evals, vision and images. Overnight: bring your own documents for Day 2.
RAG on your own notes, tool use and agents, security and production — ending in capstone demos.
One deliberately debatable claim per session, defended on stage; the strongest counter-argument gets named on the closing slide.
If autocomplete can pass your exam, your exam was never testing understanding.
Hallucination is an expected failure mode. That does not make it acceptable.
Your mother's voice is no longer proof of your mother.
Your final-year project needs a user, a baseline, and a number — not a demo.
Most production "AI agents" are a guarded while-loop in a trench coat.
There is no perfectly secure AI agent. Build one whose blast radius you can survive.
This course exists to prove a point about teaching AI, and it wants to be copied.
Every big idea arrives as a game: the room predicts, shouts, commits — then the answer lands. A brain that guessed wrong remembers forever.
Raw API calls before frameworks, your own retrieval loop before "vector database" is ever said. You earn every abstraction before you use it.
Demos that can fail live stay in the deck. Hallucinations get measured, not apologized for. The fine print is taught with the magic.
"It worked when I tried it" is not evidence. From Session 2 onward, every claim about AI quality must survive an eval.
If you only listen, you forget. Here, everyone ships — in every session, on any laptop, for free.



Karthikeyan NG heads engineering at Vision, a fintech and crypto platform in Dubai — where RAG pipelines, eval harnesses and agent guardrails are production reality, not slideware. Along the way: two startups founded, two published books on machine learning, eighteen hackathon wins, and stages at TEDx, Google, IIT Kharagpur and Seoul.
The course began where he once sat — an engineering classroom at TCE Madurai (CSE '09). He built the course he wishes he'd had, and credits most of what it teaches to the hundreds of things he shipped that failed.
Six interactive decks, six labs with notebooks and handouts, six cheatsheets, a complete learning guide, per-slide timing, and instructor prep packs. Swap Madurai for your city and run it anywhere — there is a swap-kit for exactly that.
MOCK = True offline switch every notebook carriespresenting? open any deck and press S for presenter mode — a live timer, per-slide budgets, a pace badge, and speaker notes · arrow keys navigate · F fullscreen · O overview grid
The designed path uses Google AI Studio's free tier and free Google Colab, but quotas, account access, and provider terms can change. Check access before class. If the live API is unavailable, set MOCK = True in Cell 1 of any notebook to run the offline path: every cell then runs on canned responses (prefixed [MOCK]), so the lab still teaches its lesson at reduced fidelity.
About two hours per session — roughly an hour of deck and an hour of lab. Six evenings, or one weekend. Every lab has checkpoints, so you can stop mid-way and pick up where you left off; tick sessions off in the curriculum above and this browser remembers.
Anything that opens a browser. All heavy computation happens in Google's cloud; your machine just needs a keyboard and Wi-Fi. A ₹15,000 laptop is exactly as capable here as a MacBook Pro.
One line of school math appears in the whole course: y = wx + b. If you can write a for-loop in any language, you have every prerequisite.
No. The course was born in a classroom at TCE Madurai, and the examples carry that accent on purpose — jigarthanda, Meenakshi temple, the college's own rules as a RAG corpus. Every one of them is swappable; LOCALIZATION lists what to localize and what is load-bearing. The Madurai flavour is the point, not the barrier.
Yes. The decks are self-contained and interactive, every lab has a step-by-step handout with checkpoints, and pressing S in any deck shows the full speaker narration. The Learning Guide covers every concept in prose.
The main line is built so anyone can follow it. Underneath, every deck carries collapsible depth panels — press D on a slide — that go to mechanism: logits and softmax, positional encoding and attention’s n² cost, the KV cache behind every latency and caching claim, MoE and distillation, reranking and cross-encoders, retrieval metrics, agent trajectory evaluation, and why prompt injection has no fix. They are collapsed by default, so they never slow the room down. Part 8 of the Learning Guide is the same material in prose.
Assume free-tier conversations may train future models. The course drills one rule from Session 1: never paste anything you couldn't survive seeing on the front page of the newspaper.
That is half the point. The scoping rule: one user, one data source, one measurable claim. Your Session 4 RAG notebook plus Session 2's eval harness is already the skeleton; what turns it into a project is a person-written test set, a baseline you beat, documented failures, and cost/latency arithmetic. College Project Tracks gives scoped codebase RAG, multimodal document QA, evaluation dashboards, department knowledge services, and subject-tutor ideas. Learning Guide 7.5 explains the measurement principle.
To measurement, which is where application-layer research lives. The course already teaches the method: baselines, one variable at a time, sample size, spread over mean. Learning Guide 7.6 shows where papers appear and how to read them. Good student research questions include multilingual evaluation, chunking strategies, judge bias, and injection-defense measurement.
Please do — that's the point. Teach This Yourself covers running it at any scale, and the Madurai references are designed to be swapped for your own city's.
Six sessions. Six things you ship. One honest claim: after this you can explain how a language model works — and build something on top of it that you can measure.