Ben Jervis

My lessons are calm, structured, and focused on building real understanding — not just memorising answers for exams.

Each session is shaped around what the student needs most, but most lessons follow a simple, predictable flow so students always know what to expect and feel comfortable.

Lesson structure

We usually work in three parts:

1. Quick check-in (5–10 mins)
We start by going over what the student has been working on, what’s been difficult, and anything from school or homework they want to focus on.

2. Teaching & guided practice (30–40 mins)
This is the main part of the lesson. I explain topics step-by-step, often using real examples and breaking problems down into small, manageable parts.

For programming, we build things together and I explain why each step works, not just what to type.
For theory, we focus on understanding key ideas and how they appear in exam questions.

3. Independent practice & exam focus (10–15 mins)
Students then try questions themselves with support. We often use real exam-style questions so they become familiar with the format and marking scheme.

We finish by summarising what’s been learned and setting a clear focus for next time.

?

What makes my approach different
A lot of students struggle in Computer Science not because they’re “bad at it”, but because things are often taught too quickly or too abstractly.

I focus on:

* Breaking complex topics into simple, logical steps
* Building confidence in programming through repetition and clarity
* Teaching how to think like the examiner, not just revise content
* Helping students move from confusion ? understanding ? independence