The Secret to Revising A-Level Computing (It’s Not What Most Students Think)

A-Level Computing is one of those subjects that looks deceptively manageable.

Many students think:

“I use computers every day… how hard can it be?”

Then the exam arrives.

Suddenly they discover that:

• knowing how to use technology,
• and understanding how computers actually work,

are very different things.

And that’s where many students struggle.

---

The Biggest Mistake Students Make

The most common revision mistake in A-Level Computing is treating it like a memory-only subject.

Students often:

• read notes repeatedly,
• highlight textbooks,
• watch videos passively,
• memorise definitions,

but never actually apply the knowledge.

Computing is much closer to Maths and Physics than many students realise.

You do not truly understand something until you can:

• explain it,
• apply it,
• debug it,
• or use it to solve a problem.

---

The Real Secret: Active Revision

The students who improve fastest are usually the ones who actively do things.

That means:

• writing code,
• tracing algorithms,
• drawing diagrams,
• explaining concepts aloud,
• answering exam questions,
• correcting mistakes.

Passive revision feels comfortable.

Active revision feels difficult.

But difficult revision is usually the revision that works.

---

1. Learn the Theory Like a Story

A-Level Computing contains a huge amount of theory:

• CPU architecture,
• networking,
• databases,
• cybersecurity,
• operating systems,
• logic gates,
• legal and ethical issues.

Students often try to memorise isolated facts.

Instead, try to understand the story behind the technology.

For example:

Networking

Don’t just memorise:

• packets,
• routers,
• protocols.

Understand what is physically happening.

Imagine:

• a video call,
• packets travelling,
• delays,
• lost packets,
• reassembly,
• encryption.

When the theory becomes visual and logical, it becomes far easier to remember.

---

2. Practise Programming Every Week

Programming is not something you revise once before the exam.

It is a practical skill.

Nobody learns piano by reading about piano playing.

Programming is similar.

The secret is frequency.

Even:

• 20 minutes a day,
• small coding exercises,
• debugging old programs,

can make a massive difference.

The best programmers at A-Level are not usually the students who write the most advanced code.

They are the students who:

• stay calm,
• break problems down,
• and debug methodically.

---

3. Learn to Trace Code Properly

One of the hidden superpowers in A-Level Computing is code tracing.

Students often rush.

Instead:

• track variables carefully,
• use tables,
• follow loops step by step,
• predict outputs before running code.

This is especially important for:

• recursion,
• searching,
• sorting,
• arrays,
• file handling.

Examiners love questions where students panic and lose track halfway through.

Slow thinking often beats fast thinking.

---

4. Use Past Papers Early

Many students leave past papers too late.

That’s a mistake.

Past papers teach students:

• how questions are worded,
• what examiners actually want,
• how marks are awarded,
• common traps.

In Computing, exam technique matters enormously.

Two students may understand the same topic equally well —
but the student who understands exam structure usually scores higher.

---

5. Don’t Ignore the Written Questions

Students often focus entirely on programming.

But many marks are found in:

• evaluation,
• comparison,
• advantages/disadvantages,
• ethics,
• impacts of technology.

These questions require:

• precise language,
• structured answers,
• balanced arguments.

A surprising number of students lose easy marks simply because they answer too vaguely.

---

6. Build Things

One of the best ways to revise Computing is to create projects.

Small projects force students to combine:

• logic,
• planning,
• debugging,
• testing,
• persistence.

That might be:

• a simple game,
• a database,
• a weather app,
• a revision quiz,
• a Raspberry Pi project,
• a website.

Real projects reveal understanding gaps very quickly.

---

7. Explain Concepts to Somebody Else

If you can teach a topic clearly, you probably understand it.

Try explaining:

• RAM vs ROM,
• TCP/IP,
• binary shifts,
• normalization,
• object-oriented programming,

to:

• a parent,
• a friend,
• or even an empty room.

The moment you struggle to explain something clearly usually reveals what you still need to revise.

---

AI Is Changing Revision

Modern students also have something previous generations never had:
AI tools.

Used properly, AI can:

• generate practice questions,
• explain difficult concepts,
• create debugging exercises,
• simulate interviews,
• produce alternative examples.

But there is a danger.

If students let AI do all the thinking, they learn very little.

The real value comes when students:

• attempt the problem first,
• compare their thinking,
• and analyse mistakes.

AI works best as a tutor — not as a shortcut.

---

Final Thought

The secret to revising A-Level Computing is not endless reading.

It is interaction.

The students who improve most are usually the ones who:

• practise regularly,
• make mistakes,
• debug calmly,
• explain ideas,
• and actively engage with the subject.

Computing rewards thinkers.

And like programming itself, progress usually happens:
one bug fix at a time.

 

Why Buffer Calculations Look Terrifying… But Are Actually One of the Easiest Questions in A-Level Chemistry

There’s a moment in many A-Level Chemistry lessons where students see a buffer calculation for the first time and immediately panic.

Suddenly there are:

• strange equations,
• logarithms,
• weak acids,
• salts,
• Ka values,
• and lots of brackets.

It looks horrible.

But here’s the surprise:

Buffer calculations are often some of the most predictable and methodical questions on the paper.

Once you understand what the examiner is actually asking, the whole topic becomes far easier than students expect.

---

What Is a Buffer?

A buffer solution is simply a solution that resists changes in pH when small amounts of acid or alkali are added.

There are two common types:

• Acidic buffer → weak acid + its salt
• Alkaline buffer → weak base + its salt

At A-Level, students are normally asked to:

1. identify the buffer,
2. substitute values into an equation,
3. calculate the pH.

That’s it.

---

The Real Secret

Students often think buffer questions are difficult because they try to memorise everything.

But most questions reduce to one idea:

Acid Buffer Equation

$pH = pK_a + \log\left(\frac{[salt]}{[acid]}\right)$

You are simply comparing:

• how much weak acid you have,
• to how much salt you have.

If the concentrations are equal:

• the log term becomes zero,
• so pH = pKa.

That single idea solves a huge number of exam questions.

---

Example 1 — Acid Buffer

Suppose we mix:

• 0.50 mol dm⁻³ ethanoic acid
• 0.30 mol dm⁻³ sodium ethanoate

Ethanoic acid has:

And that’s the entire calculation.

No magic.
No terrifying chemistry.
Just substitution into a formula.

---

Example 2 — Alkaline Buffer

An alkaline buffer contains:

• ammonia solution,
• ammonium chloride.

For alkaline buffers, students often use the pOH equation first.

Suppose:

• ammonia concentration = 0.40 mol dm⁻³
• ammonium chloride concentration = 0.25 mol dm⁻³

For ammonia:

Again:

• identify the equation,
• substitute carefully,
• use the calculator correctly.

---

Why Students Lose Marks

The maths is usually not the problem.

The real problems are:

• using the wrong concentration in the ratio,
• forgetting to convert pOH to pH,
• calculator mistakes with logs,
• panic caused by the appearance of the equation.

In lessons, I often find students can solve buffer questions perfectly once they slow down and treat them as a simple substitution exercise.

---

Practical Chemistry Makes Buffers Easier

Buffers make far more sense when students actually see them working.

In the lab:

• universal indicator,
• pH probes,
• PASCO sensors,
• adding acid and alkali gradually,

all help students understand what the equations are really describing.

Once students realise the buffer is simply “absorbing” added H⁺ or OH⁻ ions, the calculations suddenly feel logical rather than abstract.

---

Final Thought

Buffer calculations are a wonderful example of something in A-Level Chemistry that looks frightening but is actually very structured.

The students who succeed are rarely the ones who memorise blindly.

They are the students who:

• recognise the pattern,
• stay calm,
• substitute carefully,
• and trust the process.

Sometimes the scariest-looking questions are secretly the easiest.

 

Pascal’s Vases – Different Shapes, Same Pressure?

One of the most surprising demonstrations in physics is discovering that the shape of a container does not determine the pressure at the bottom.

At first glance, students are convinced it must.

A tall thin vase looks as though it should exert less pressure than a wide heavy-looking one.

Surely the container holding more water must produce the greatest pressure?

That is exactly why Pascal’s Vases are such a useful teaching demonstration.

What Are Pascal’s Vases?

Pascal’s Vases are a set of differently shaped containers connected to the same base.

Typically:

• One is tall and narrow
• One widens outwards
• One narrows towards the top
• Another may have curved sides

Despite their different shapes and water volumes, when the water level is the same height, the pressure at the base is also the same.

That idea feels completely wrong to many students at first.

And that is what makes the experiment memorable.

The Key Physics Idea

Hydrostatic pressure depends on:

• The density of the liquid
• Gravity
• The depth of the liquid

Not the total volume.

The equation is:

$P=\rho gh$

Where:

• $P$ = pressure
• $\rho$ = density
• $g$ = gravitational field strength
• $h$ = depth of liquid

The width or shape of the container does not appear in the equation at all.

That is the important conceptual breakthrough.

Experiment 1 – Comparing Water Pressure

The simplest experiment is to fill each vase to exactly the same height.

Students predict which vase will create the largest pressure at the bottom.

Most choose the widest one because it contains the most water.

Using:

• A pressure sensor
• A manometer
• Or even observing water jets from holes at the base

students quickly discover the pressure is identical.

This creates one of those excellent “That can’t be right…” moments in the lab.

And those moments are where real learning starts.

Experiment 2 – Water Jets

If each vase has a small hole at the same depth, the water jets travel roughly the same horizontal distance.

Again, students expect the larger vase to produce a more powerful stream.

But the speed of the water leaving depends mainly on the pressure due to depth.

Equal depth → equal pressure → similar jet behaviour.

A wonderfully visual demonstration.

Experiment 3 – Measuring Force on the Base

This experiment often causes even more confusion.

Different shaped vessels can contain different masses of water while producing the same pressure at the base.

Students naturally assume:

“More water means more downward force.”

But some of the weight is supported by the sides of the container depending on the shape.

This opens discussions about:

• Resultant forces
• Vector components
• Pressure vs total force
• Engineering design

It is an excellent bridge between GCSE and A-Level thinking.

Experiment 4 – PASCO Pressure Sensors

Using modern PASCO pressure sensors connected to software such as PASCO Capstone transforms the experiment.

Students can:

• Record live pressure readings
• Compare multiple vessels
• Plot pressure against depth
• Investigate linear relationships

The graph obtained is typically a straight line:

$P\propto h$

Students can then experimentally verify the hydrostatic pressure equation rather than simply memorising it.

That is a far deeper level of understanding.

Common Student Misconceptions

“More water means more pressure.”

Not necessarily.

Pressure depends on depth, not volume.

---

“Wider containers push harder.”

Only if the depth changes.

---

“Pressure and force are the same thing.”

They are closely related but not identical.

Pressure is force per unit area.

$P=\frac{F}{A}$

Pascal’s Vases help students separate these ideas clearly.

Why Demonstrations Matter

Students often understand equations only superficially.

But seeing identical pressure readings from wildly different vessels creates a mental conflict that forces genuine understanding.

That is why practical demonstrations remain so important in physics teaching.

A surprising experiment is remembered far longer than a copied note.

And Pascal’s Vases are full of surprises.

 

Why Mechanics Questions Go Wrong (It’s Not the Maths… It’s the Setup)

“Most students lose marks in mechanics before they even start the maths.”

---

The Real Problem with Mechanics

Ask most A-Level Maths students what they struggle with, and mechanics comes up again and again.

But here’s the surprising truth:

It’s not the algebra
It’s not the equations
 It’s not even Newton’s Laws

It’s the setup.

Students rush in, start writing equations… and everything goes wrong from the very first line.

---

Why This Topic Matters

Mechanics questions are:

• Highly structured
• Predictable in content
• Generous with marks

And yet…

They consistently produce avoidable mistakes.

From years of teaching (and recent sessions like those with Isaac), the pattern is clear:

Students don’t lose marks because they can’t do the maths.
They lose marks because they haven’t understood the situation.

---

Step 1: What Is Actually Happening?

Before writing anything down, students need to answer:

What is physically happening here?

Is the object:

• Stationary?
• Accelerating?
• Moving at constant velocity?

Is it:

• On a slope?
• Hanging on a string?
• In contact with a surface?

Teaching insight

Stronger students pause here.
Weaker students skip this entirely.

---

Step 2: Draw a Clear Force Diagram

This is where most marks are won—or lost.

A good force diagram should:

• Include all forces
• Show correct directions
• Be neatly separated from the question

Common missing forces:

• Weight ($𝑚𝑔$)
• Normal reaction
• Tension
• Friction

Classic mistake:

Students draw a diagram… but don’t use it.

The diagram is the question.

---

Step 3: Choose the Right Axes

This is the step that transforms the question.

Instead of sticking with horizontal/vertical axes:

Rotate your axes to match the problem

For slopes:

• One axis parallel to the slope
• One axis perpendicular to the slope

Why this matters:

• Eliminates unnecessary trig mistakes
• Simplifies equations
• Makes forces easier to interpret

---

Step 4: Understand the Forces Properly

Students often name forces correctly… but don’t understand them.

Tension

• Pulls away from the object
• Same throughout a light string

Normal Reaction

• Always perpendicular to the surface
• Not always equal to weight

Weight

• Always acts vertically downward

---

The Biggest Issue: Not Reading the Question

This is the uncomfortable truth.

Students often:

• Miss key words like “constant velocity”
• Ignore phrases like “smooth surface”
• Fail to notice what they’re actually solving for

Example:

• “Constant velocity” → acceleration = 0
• “Smooth” → no friction
• “Find the tension” → not the acceleration

These are not maths errors.
These are reading and thinking errors.

---

Step 5: The Correct Thinking Process

Here’s the structure that works every time:

1️⃣ What is happening physically?

2️⃣ What forces are acting?

3️⃣ Which direction is easiest?

4️⃣ Apply Newton’s Second Law

5️⃣ Solve the maths

In that order.

Not the other way round.

---

Why Students Go Wrong

• They rush into equations
• They skip diagrams
• They don’t visualise the situation
• They treat mechanics like algebra

---

Why 1:1 Tuition Changes Everything

This is where individual teaching makes a huge difference.

In a classroom:

• Mistakes go unnoticed
• Diagrams aren’t checked carefully
• Thinking isn’t challenged

In 1:1 sessions:

• Every step is questioned
• Every diagram is corrected
• Every misunderstanding is addressed immediately

Teaching becomes less about delivering content…
and more about fixing thinking.

---

Final Thought

Mechanics isn’t difficult.

But it is different.

And once students realise:

The marks come from understanding first, maths second

Everything starts to fall into place.

 

Why Internal Resistance Confuses Everyone (And How to Actually Understand It)

“Your battery says 9V… so why does your circuit only get 7.8V? Where did the rest go?”

---

The Hidden Concept That Costs Marks

Internal resistance is one of those A-Level Physics topics that looks simple—until students hit exam questions.

They can often:

• Rearrange equations ✔
• Do calculations ✔
• Recognise circuits ✔

But ask them what’s actually happening, and things quickly fall apart.

That’s because internal resistance isn’t just maths.

It’s energy, physics, and real-world behaviour all wrapped into one.

---

EMF vs Terminal Potential Difference (The Core Confusion)

This is where most problems begin.

EMF (ε)

• The total energy supplied per unit charge
• What the battery could provide
• Measured when no current flows

Terminal Potential Difference (V)

• The actual energy delivered to the circuit
• What the components really get
• Measured when current is flowing

The Key Idea

The battery does not give all its energy to the circuit.

Some is lost inside the battery itself.

---

Where Does the “Lost Voltage” Go?

That missing voltage isn’t “lost” in a mysterious way.

It’s converted into heat inside the battery.

Inside every cell is resistance—just like a resistor in your circuit.

So when current flows:

• Energy is transferred inside the battery
• The battery warms up (sometimes noticeably)
• Less energy reaches the external circuit

The Equation Behind It

$$𝑉=𝜀-𝐼𝑟$$

Where:

• $𝜀$= EMF
• $𝐼$= current
• $𝑟$ = internal resistance

---

Why Voltage Drops Under Load

When no current flows:

• $𝐼=0$
  
• $𝑉=𝜀$
  

But as soon as you connect a circuit:

• Current flows
• The term $𝐼𝑟$ increases
• Terminal voltage drops

Simple way to think about it:

The harder the battery works (more current), the more energy it wastes internally.

---

The Practical (Where It Finally Clicks)

This is where your teaching setup really shines.

Students understand internal resistance when they see it happening.

Practical approach:

• Use a variable resistor to change current
• Measure:
  • Current (I)
  • Terminal voltage (V)
• Plot a graph of V vs I

What they observe:

• A straight line
• Negative gradient = internal resistance (r)
• Y-intercept = EMF (ε)

Suddenly, it’s not abstract anymore—it’s measurable.

---

Common Exam Mistakes (And How to Fix Them)

1. Mixing up EMF and voltage

Students treat them as the same thing.

✔ Fix:

• Always ask: Is current flowing?
• If yes → it’s terminal p.d., not EMF

---

2. Ignoring internal resistance entirely

Students use $𝑉=𝐼𝑅$ blindly.

✔ Fix:

• Look for clues:
  • “Battery”
  • “Cell”
  • “Terminal voltage”
• These usually signal internal resistance is involved

---

3. Not interpreting graphs properly

Students can plot but not explain.

✔ Fix:

• Practise linking:
  • Gradient → internal resistance
  • Intercept → EMF

---

4. No physical understanding

They calculate correctly—but don’t explain energy loss.

✔ Fix:

• Use phrases like:

  “Energy is dissipated as heat within the cell due to internal resistance.”

---

The Big Picture

Internal resistance isn’t just an exam topic.

It explains:

• Why batteries get warm
• Why devices lose efficiency
• Why high currents are problematic
• Why real circuits never behave perfectly

---

Final Thought

Once students stop seeing internal resistance as just an equation and start seeing it as:

energy being shared between the circuit and the battery itself

Everything clicks.