Variables and Data Types

Active learning works for variables and data types because students need to experience type errors firsthand to understand why conversions matter. When they see their code break due to mixing strings and integers, the concept sticks better than any explanation.

• Year 8
• Computing
• 4 activities
• 20 min–35 min

Learning Objectives

1. Classify data into appropriate Python data types (integer, float, string, boolean) based on given values.
2. Calculate the results of arithmetic operations between variables of compatible numeric data types.
3. Explain the difference between string concatenation and numerical addition using Python code examples.
4. Analyze the impact of variable naming conventions on code readability and maintainability.
5. Predict the outcome of operations involving variables of different, incompatible data types without explicit conversion.

Peer Teaching

⏱ 35 min·Pairs

Pair Programming: Type Challenges

Pairs create variables for each data type and write code to perform operations, such as adding two integers or concatenating strings. They input user data with input() and convert types using int() or str() to avoid errors. Pairs then swap scripts to test and debug each other's code.

Prepare & details

Justify why it is important for a computer to know if data is a number or text.

Facilitation Tip: During Pair Programming: Type Challenges, circulate to listen for partners explaining why their code crashed, turning run-time errors into teachable moments.

Setup: Presentation area at front, or multiple teaching stations

Materials: Topic assignment cards, Lesson planning template, Peer feedback form, Visual aid supplies

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

Peer Teaching

⏱ 30 min·Small Groups

Small Groups: Naming Refactor Relay

Provide groups with poorly named code snippets using vague variables like x1 or temp. Each student improves names for clarity, passes to the next for testing, and discusses how changes affect readability. Groups present one refactored example to the class.

Prepare & details

Analyze how the choice of variable names affects the maintainability of code.

Facilitation Tip: In Small Groups: Naming Refactor Relay, require groups to explain their naming choices to you before moving on, reinforcing the connection between names and readability.

Setup: Presentation area at front, or multiple teaching stations

Materials: Topic assignment cards, Lesson planning template, Peer feedback form, Visual aid supplies

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

Peer Teaching

⏱ 20 min·Whole Class

Whole Class: Prediction Whiteboard

Display code snippets mixing data types on the board or screen. Students predict outputs individually on mini-whiteboards, then reveal results by running code. Discuss surprises and vote on fixes as a class.

Prepare & details

Predict the consequences of using the wrong data type in a simple calculation.

Facilitation Tip: For the Whole Class: Prediction Whiteboard, ask students to raise their hands only after they have written their predictions, giving everyone time to think independently before group discussion.

Setup: Presentation area at front, or multiple teaching stations

Materials: Topic assignment cards, Lesson planning template, Peer feedback form, Visual aid supplies

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

Peer Teaching

⏱ 25 min·Individual

Individual: Personal Data Script

Students write a script storing their name (string), age (int), height (float), and UK resident status (bool). They print formatted outputs and perform a simple calculation, like age next year.

Prepare & details

Justify why it is important for a computer to know if data is a number or text.

Facilitation Tip: For the Individual: Personal Data Script, model how to test edge cases like empty strings or negative numbers to build resilience against common input errors.

Setup: Presentation area at front, or multiple teaching stations

Materials: Topic assignment cards, Lesson planning template, Peer feedback form, Visual aid supplies

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

Teaching This Topic

Experienced teachers approach this topic by making errors visible and unavoidable. Avoid starting with definitions—let students discover rules through debugging. Use whiteboard predictions to confront misconceptions head-on, as research shows preemptive explanations often fade when students encounter real code. Emphasize that type awareness is a habit, not a one-time lesson, so reinforce naming and conversion checks in every subsequent activity.

What to Expect

Successful learning looks like students confidently assigning types, converting inputs correctly, and naming variables appropriately without prompting. They should also predict output differences between integers and floats before running code, showing they grasp the underlying logic.

Watch Out for These Misconceptions

Common Misconception

During Pair Programming: Type Challenges, watch for students assuming input() returns the correct type for calculations.

What to Teach Instead

Interrupt their debugging to ask, 'What type does input() return? How can you verify this?' Then have them add a type() check before conversion to reinforce the habit.

Common Misconception

During Small Groups: Naming Refactor Relay, watch for groups using names that don’t describe the variable’s purpose, like 'x' for age.

What to Teach Instead

Pause the activity to ask, 'If someone else reads your code in six months, will they know what x represents?' Direct them to rename variables using the relay’s structure to practice descriptive naming.

Common Misconception

During Whole Class: Prediction Whiteboard, watch for students treating integers and floats as interchangeable in operations.

What to Teach Instead

After predictions, run the code together and ask, 'Why did 3 + 2.0 give 5.0 instead of 5?' Use this moment to contrast integer and float behavior explicitly.

Assessment Ideas

Quick Check

After the Whole Class: Prediction Whiteboard activity, ask students to submit their corrected predictions for mixed-type operations, such as 5 + '2' and 3.0 * 2. Use this to assess whether they understand the need for type conversion.

Exit Ticket

After Small Groups: Naming Refactor Relay, have students submit one refactored variable name from their group’s code along with a sentence explaining why the new name is clearer. Collect these to assess naming rule application.

Discussion Prompt

During Pair Programming: Type Challenges, ask pairs to explain their error messages to the class, focusing on how they diagnosed the type conflict. Listen for mentions of input() returning strings and int() conversions.

Extensions & Scaffolding

• Challenge: Ask early finishers to write a script that takes user input for a temperature in Celsius, converts it to Fahrenheit, and classifies it as 'cold', 'warm', or 'hot' based on thresholds.
• Scaffolding: For struggling students, provide a partially completed script with comments guiding where to add type conversions and variable names.
• Deeper exploration: Explore the limits of float precision by having students compare 0.1 + 0.2 with 0.3 and discuss why the results differ, introducing the concept of floating-point representation.

Key Vocabulary

Variable	A named storage location in a computer's memory that holds a value. This value can change during program execution.
Data Type	A classification that specifies which type of value a variable can hold and what operations can be performed on it. Common types include integers, floats, strings, and booleans.
Integer (int)	A whole number, positive or negative, without decimals. For example, 10, -5, or 0.
String (str)	A sequence of characters, such as letters, numbers, and symbols, enclosed in quotation marks. For example, 'hello' or 'Year 8'.
Boolean (bool)	A data type that can only have one of two values: True or False. Often used for logical conditions.