back

0% Completed

Contents
Codebasics Icon
Script Studio

Prev Next
Script Studio
ART OF TEACHING @ CODEBASICS · CHAPTER 4
Script Studio
Write a 90-second explanation script using the Codebasics Method: pain point → analogy → bite-sized chunks.
Codebasics INC
How it works
1
Pick one topic — something technical you might really teach.
2
Build your script in 3 moves, one screen each. AI tools are allowed for polish, but the thinking must be yours.
3
Self-check against the technique checklist, compare with a Codebasics sample, download your script as a PDF.
STEP 1 OF 5
Pick your topic
Choose the one furthest from your comfort zone.
What is Kafka?
Explain it to a backend developer who has only used REST APIs.
What is Power BI?
Explain it to a store manager who lives in Excel.
What is Statistical ML?
Explain it to a smart 12th-standard student.
STEP 2 OF 5
Move 1 — Open the wound (pain point)
Write 2–3 sentences that make your audience FEEL the problem before you name any tool. No product names allowed yet.
See a Codebasics example
Kafka example: “Your food-delivery app just hit 1 million orders a day. Payments, live tracking, notifications - every service is screaming at every other service, and last night the whole thing collapsed for 40 minutes. Somewhere, an order for biryani vanished.”

Notice: no mention of Kafka. Only the pain.
STEP 3 OF 5
Move 2 — Bring the analogy
Introduce the idea through something your audience already knows from daily life. One analogy, carried honestly.
See a Codebasics example
Kafka example: “Now imagine a post office in the middle of the city. Services don’t shout at each other anymore - they drop letters at the post office, and whoever needs them picks them up, at their own pace. Nobody vanishes. That post office is Kafka.”
STEP 4 OF 5
Move 3 — Break it into chunks
List the 3 bite-sized chunks you would teach next, one line each, in order. One idea per chunk — connect the dots gradually.
See a Codebasics example
Kafka example:
1. Producers & consumers - who drops letters, who collects them.
2. Topics - the labeled pigeonholes letters are sorted into.
3. Why it never loses a letter - replication, in one simple picture.
STEP 5 OF 5
The technique checklist
Read your script aloud once. Then be ruthless — tick only what is TRUE.
YOUR RESULT
– / 6
Complete the steps above
(If the buttons are not interactive in your LMS view, score yourself using the reveals above.)
Compare with the full Codebasics sample script
Full Codebasics sample (Kafka, ~85 seconds):

“Your food-delivery app just hit a million orders a day - and last night it collapsed for 40 minutes because every service was shouting at every other service. An order for biryani simply vanished. Now picture a post office in the middle of the city. Services stop shouting; they drop letters at the post office, and whoever needs them collects them at their own pace. That post office is Kafka. Three things make it work. First, producers and consumers - who drops letters, who collects them. Second, topics - labeled pigeonholes the letters are sorted into. Third, replication - the reason no letter is ever lost, even if a whole shelf burns down. And that is why, next time you hit a million orders, nobody’s biryani disappears.”
A script this good deserves a camera.
Record this exact script on your phone — it is perfect practice for your Stage 1 re-record. Download your script below and keep it beside the lens.
Codebasics INC · Art of Teaching Crash Course · Chapter 4 — Script Studio