Skip to content

demo-lesson-script.md

Latest commit

 

History

History
111 lines (67 loc) · 7.22 KB

demo-lesson-script.md

File metadata and controls

111 lines (67 loc) · 7.22 KB
Raw

Demo Lesson Script — "Hello, Python!" (15-20 min)

A word-for-word script for your selection demo lesson. It uses Lesson 1 (code-examples/lesson01_hello_world.py) and the slides (slides/lesson01.md). Read it twice, then rehearse once standing up. The whole thing is 15-20 minutes including an interactive bit the panel will love.

Before you start (2 min of prep):

  • Have open, in this order: a terminal (or IDLE) ready, then code-examples/lesson01_hello_world.py.
  • Make sure the terminal window is large enough for the panel to see text.
  • Have python code-examples/lesson01_hello_world.py typed but not yet run.

1. Opening — hook (2 min)

"Good morning. Before I introduce myself, I have one question for you. How does your phone's calculator add two plus two? ... (pause, let someone answer) ... It doesn't know. Somebody had to write the instructions for it. That list of instructions is called a program, and the person who writes it is a programmer. Today I am going to show you how to write your very first program — in Python."

(Key: this is not about Python yet — it is about why programming matters. This shows you can hook non-technical students.)

2. The two-run demo (10 min)

(Keep talking WHILE typing — never a silent pause.)

"Python is a programming language. It was created in the Netherlands in 1991, and today it powers YouTube, Google, and NASA. But its real superpower for a school like ours is this — it reads almost like English. Watch."

Step 1 — run the file. Press Enter.

Hello, World!
Namaste Nepal!

"That is a real Python program. The command is print — whatever is inside the brackets appears on the screen. Now, two things to notice. First, the text has to be inside quotation marks — those tell Python 'this is text, not code'. Second, Python ran my two lines from top to bottom, in order. That single idea — top to bottom, one line at a time — is called sequence, and it is the first and most important rule of every program."

(Panel note: saying "sequence" shows you know the formal CS term. It maps to the NEB Unit 5 concept of program flow.)

Step 2 — one line at a time (optional if time).

"I want to prove to you that Python isn't guessing — it's following instructions one by one."

Type, and run each:

print(7 + 5)     # -> 12
print(10 / 4)    # -> 2.5
print(10 // 4)   # -> 2
print(10 % 4)    # -> 2

"Look at these three. 10 / 4 gives 2.5 — normal division. But 10 // 4 gives 2 — that's whole-number division. And 10 % 4 gives 2 — that's the remainder. So a simple school problem — 'divide 10 biscuits among 4 students, what's left over?' — is exactly what this language can answer. This is how we will connect Python to maths your students already know."

(Panel note: connecting to a relatable classroom example is what teachers get interviewed for.)

Step 3 — the surprise.

"Now the part that makes beginners feel like magicians. A computer can repeat work forever without getting bored. Watch this — I am going to make it print a new line using \n."

print("Line 1\nLine 2\nLine 3")

"That backslash-n is the symbol for 'new line'. Notice I wrote it ONCE and the computer followed the instruction. In our next lesson we'll make the program ask questions and make decisions — that is where it really comes alive."

3. Students try it (5 min)

(Give the panel a real student task. This demonstrates your active-learning style.)

"Now your turn — and I want you to predict before you type. Take this program and tell me what it prints:"

print(17 % 5)

(Let one person answer. Accept 1 or 2 guesses — do NOT reveal. Then type and run: it prints 2.)

"Who guessed 2? ... That's the remainder when 17 is divided by 5. Now, in the notebook, write one line of Python that prints your name. That is your exit ticket — I'll check it as I walk around."

(Panel note: "predict-then-run" and "exit ticket" are two professional teaching techniques. Say them out loud so the panel hears them.)

4. Wrap-up (2 min)

"Today you learned three things. One — a program is a list of instructions. Two — print shows text on the screen, and text needs quotation marks. Three — Python runs top to bottom. For homework, I want you to predict what 2 ** 5 prints — that little ** is a secret operator I haven't taught you yet. Bring me your guess next class, and we'll check it together. Thank you."

(Panel note: ending with a "discovery homework" shows you plan follow-up, not one-off lessons.)

Likely panel questions + model answers

Q1. The NEB syllabus uses C, not Python. Why Python?

"Python and C teach the same concepts — sequence, decisions, loops, arrays, functions. Python just removes the typing overhead, so a student in Grade 10 can write their first working program in ten minutes instead of one period. Everything they learn transfers directly to C. The curriculum-map.md in my pack maps each Python lesson to the NEB outcomes, and has a Python-to-C side-by-side table."

Q2. What if the school has very few computers?

"I plan for it. The worksheets are built around dry-run — tracing a program's output on paper, which is exactly the skill the NEB exam rewards. I also use one teacher machine with a projector for live coding, rotate small groups at the machines, and if internet exists, a browser-based compiler like replit.com runs on cheap phones with zero installation."

Q3. How will you assess students?

"Three layers: worksheets every lesson (most are paper-based), one small project every two lessons, and a practical exam at term end where students run two programs and explain a trace table. Every program in my pack runs — I tested all of them."

Q4. What do students struggle with most, and how do you handle it?

"Four things, in order: forgetting the colon after if/for, forgetting to indent, using = instead of ==, and forgetting that input() returns text. I don't just mention these — each lesson plan has a 'common mistakes' table and I put the biggest one on a slide so they see it coming."

Q5. What would you teach if you only had one week?

"One week, Grades 10-12: Day 1 print and variables, Day 2 input and conditionals, Day 3 loops, Day 4 lists and functions, Day 5 — students build a grade calculator from scratch. That single program exercises everything and gives them something to show their families."

Q6. How do you keep the class engaged?

"Every lesson opens with a question, not a definition — 'how does a calculator add?' — and every concept lands on something they already know: biscuits for remainders, football teams for sets. Students type or trace on paper within fifteen minutes of the bell. Nobody sits and watches for a full period."

Q7. Do you have materials ready?

"Yes — ten lesson plans, ten slide decks, ten worksheets with answer keys, five tested projects, and a NEB-style question bank. They're in the repository, and I can leave a copy with the school."

Rehearse the script twice: once silently, once out loud with the code running. The panel is looking for calm pacing, not perfection. If you lose your place, look at the next bold line and keep going.