Find a KS3 Computer Science tutor

Here is a short teaching example in Python. It adds the points from three rounds. The list [2, 4, 6] supplies the values; total stores the running score.

total = 0
for points in [2, 4, 6]:
    total = total + points
print(total)

A learner might predict 6, because that is the last item in the list. Follow both variables to see the difference: on the first pass, points is 2 and total becomes 2; on the second, points is 4 and total becomes 6; on the third, points is 6 and total becomes 12.

The assignment total = total + points means “calculate the old total plus these points, then store the result as the new total”. It keeps adding to the previous score. The final line is outside the loop, so the program prints 12 once. If that line were indented to sit inside the loop, it would print 2, then 6, then 12 on separate lines.

A stronger answer explains both the changing total and the position of print, rather than guessing from the last number. For a follow-up, replace the list with [1, 3, 5]. Write down the totals after each pass before running it: 1, 4, 9, with 9 printed at the end. This checks whether the learner can use the same reasoning with new values.

For a small unsigned binary number, use the place values 8, 4, 2, 1, from left to right. “Unsigned” means we are representing a non-negative whole number here. In the example 1101, the digits select which place values to include:

• The first 1 includes 8.
• The next 1 includes 4.
• The 0 leaves out 2.
• The final 1 includes 1.

So binary 1101 represents 8 + 4 + 1 = 13 in decimal, our usual number system. Adding all four place values would give 15; the zero is why that answer is wrong.

Try the reverse with 9. Keep the same labelled columns, 8, 4, 2, 1. Since 9 = 8 + 1, include the first and last columns and leave out the middle two: 1001. Explaining the zeroes matters as much as getting the digits right.

Take one piece of schoolwork to the conversation: a program that gives the wrong answer, a teacher’s comment, or a theory question your child cannot explain. It gives you something concrete to discuss when comparing a tutor’s approach. Check relevant teaching experience in the profile and ask how it relates to this age group and the school’s programming language.

Use Latimer’s free introductory meeting to discuss goals, teaching approach and arrangements before paid lessons. It is a conversation about fit, not normally a full teaching lesson. A useful first goal might be “explain a loop without running it” or “convert a small binary number and justify each place value”.

Here is a suggested structure to agree with a tutor. Keep the first goal small enough to inspect: a completed project alone may hide how much help the learner needed. For a school assessment, add the date, topic list and teacher feedback so practice addresses the actual task.

Latimer’s service centres on online one-to-one tuition. Microsoft Teams is the default meeting platform; the tutor and family can agree another method. Confirm the meeting tool and code editor before the lesson so the time can be spent on the work.

Use a device on which the learner can comfortably read and edit their code. Have the school task and a small example ready, including the expected result and what actually happened. If code fails, keep the error message: it may help identify where to start.

Use dummy information in shared files, and keep passwords and private account details out of shared work. On a school-managed device, check installation restrictions with the school before adding software. If the required editor cannot be used, agree a permitted alternative with the tutor in advance.