Education digital-technologies year-9
Chapter 1 - First Python Mission
The opening Explorer chapter introducing what code is and what it means to make a simple Python program run.
Chapter 1 frames Python as a growing mission console: a simple program that becomes more capable as each concept is added.
Chapter Navigation
Learning Intention
- understand that code is a sequence of explicit instructions
- run a basic Python program successfully
- use simple comments to explain intent
Mission Brief
The Explorer project starts as a tiny command-line console. In this chapter, the goal is not complexity, it is confidence: write a small file, run it, and verify the output.
Starter Program
"""
EXPLORER v0 — Chapter 1
A tiny mission console that prints a banner and status line.
"""
# Output banner
print("====================================")
print("EXPLORER MISSION CONSOLE")
print("====================================")
# Initial status
print("Status: online")
print("Ready for Chapter 2.")Checkpoint
- program runs without errors
- output appears in the shell exactly as expected
- comments describe why the section exists
Chapter 1: Your first Python mission
EXPLORER · v0 (seed program) · making something small that runs, makes sense, and grows with you
🧭 Mission brief
Imagine you’ve been handed a simple research tablet. Not a fancy app - just a plain screen that prints information cleanly.
Your job over the next few lessons is to build that “mission console” in Python.
It will start tiny (like, laughably tiny), then it will grow chapter by chapter until it can: remember details, collect observations, make decisions, repeat tasks, store lists of events, and stay readable even when it gets bigger.
That’s the point: you’ll learn coding by watching one program evolve.
Your job over the next few lessons is to build that “mission console” in Python.
It will start tiny (like, laughably tiny), then it will grow chapter by chapter until it can: remember details, collect observations, make decisions, repeat tasks, store lists of events, and stay readable even when it gets bigger.
That’s the point: you’ll learn coding by watching one program evolve.
What you should expect
Python will be strict. You will make mistakes. You will see errors.
That’s not a problem. That’s literally how learning to code feels.
Today the goal is simple: make your first mission console print something that proves it ran.
That’s not a problem. That’s literally how learning to code feels.
Today the goal is simple: make your first mission console print something that proves it ran.
What “code” actually means
Code is a set of instructions written so the computer can follow them. The computer won’t guess. It won’t “figure out what you meant”. It follows instructions exactly, in order.
Python is one instruction language you can use. When your Python file runs, it reads from top to bottom and does what you told it to do.
A lot of programs follow a simple rhythm:
Today, we’re going to keep “information goes in” super simple. We’ll write it into the code for now. Later, you’ll collect it from the user.
Python is one instruction language you can use. When your Python file runs, it reads from top to bottom and does what you told it to do.
A lot of programs follow a simple rhythm:
Information goes in
The program gets details from somewhere (you, a sensor, a file, or values you wrote into the code).
The program does something
It organises the info, checks it, transforms it, or makes decisions.
Something comes out
It prints results, saves a log, shows a message, or produces an answer.
Today, we’re going to keep “information goes in” super simple. We’ll write it into the code for now. Later, you’ll collect it from the user.
A habit that makes you a better coder fast
We’re going to build one habit from day one: commenting with purpose.
Comments are not there to decorate your code. They are there to explain your thinking, so the code stays readable and fixable.
The easiest style to start with is:
If your code is readable, your brain feels calmer. If your brain feels calmer, you make fewer mistakes.
Comments are not there to decorate your code. They are there to explain your thinking, so the code stays readable and fixable.
The easiest style to start with is:
You’ll see this pattern a lot
# A short header that names the section
# A short comment that explains why this section exists
# A short comment that explains why this section exists
If your code is readable, your brain feels calmer. If your brain feels calmer, you make fewer mistakes.
EXPLORER v0 (seed program)
This is intentionally small. That’s on purpose.
Your first job is to make Python print a clean “mission console” banner and a simple status line. If it prints, it ran. If it ran, you’ve begun.
Your first job is to make Python print a clean “mission console” banner and a simple status line. If it prints, it ran. If it ran, you’ve begun.
"""
EXPLORER v0 — Chapter 1
A tiny mission console that prints a banner and a status line.
This is our starting point. We will upgrade this program over time.
"""
# =========================
# OUTPUT (what appears on screen)
# =========================
# Right now, our mission console only needs to prove it can run and print.
print("====================================")
print(" EXPLORER CONSOLE ")
print("====================================")
print("Status: online ✅")
Make it feel like your console
Change the words inside the
Keep it clean and readable. When your program runs, the output should look intentional — not messy.
If you break something and Python throws an error, don’t panic. Errors are just Python telling you: “I can’t follow this instruction.” We’ll get good at reading them later. For now, fix the simplest causes: missing quotes, missing brackets, or a line that got half-deleted.
print() lines. Make the console sound like it belongs to a mission you’d actually want to run. Keep it clean and readable. When your program runs, the output should look intentional — not messy.
If you break something and Python throws an error, don’t panic. Errors are just Python telling you: “I can’t follow this instruction.” We’ll get good at reading them later. For now, fix the simplest causes: missing quotes, missing brackets, or a line that got half-deleted.
Next time
In Chapter 2,
That’s where coding starts to feel less mysterious and a lot more controllable.
print() stops being “just for display” and becomes one of your best tools for understanding what your code is doing while it runs. That’s where coding starts to feel less mysterious and a lot more controllable.