By Cyril KimbiThe Computer Science practical is the paper where knowing the theory and passing the paper are furthest apart. Candidates who can describe an algorithm perfectly lose marks because they cannot produce working code under time, with a clock running and no compiler to lean on.
The gap between knowing and doing
Reading code and writing code are different abilities, and only one of them is examined.
You can follow a worked solution completely, understand every line, and still be unable to produce it on a blank page. That experience is not a sign you misunderstood — it is the normal result of practising recognition instead of production.
The fix is uncomfortable and simple: close the book and write the program from scratch. Every time. If you cannot, you have found exactly what to work on.
The patterns worth automating
Most practical questions are built from a handful of structures. Know these well enough to write them without thinking:
- Input with validation — read a value, reject it if out of range, ask again.
- Counting and accumulating — running totals, averages, largest and smallest.
- Arrays — filling, traversing, finding.
- Linear and binary search, and when each applies.
- One sorting algorithm, written correctly from memory.
- File handling — open, read a record, process, close.
- Nested loops, especially for tables and patterns.
Almost every question recombines these. A candidate fluent in seven patterns handles an unfamiliar question by assembling them; a candidate who memorised twenty complete programs is stuck the moment the question differs.
Writing code on paper
This is the specific skill the paper tests, and it must be practised in the form it is examined.
- Indent visibly. Structure is marked, and an examiner who cannot see where a loop ends cannot award it.
- Declare your variables with sensible names. Marks are given for declarations.
- Write the loop bounds carefully. Off-by-one errors are the single most common loss.
- Comment the non-obvious steps briefly — they show intent, and intent earns method marks when the code is imperfect.
- Do not erase and rewrite. Cross out cleanly; a rewritten answer under time pressure usually gets worse.
Pseudocode questions have their own rule: be consistent. Pick one convention for assignment, input, output and loops, and use it throughout. Examiners accept a range of conventions; they do not accept three in one answer.
Tracing: the skill that carries the most marks
Trace tables appear on almost every paper and are among the most reliably earned marks, because they require no creativity at all — only discipline.
Method: draw a column for every variable, plus one for output. Then execute one line at a time, writing the new value in the correct row. Do not skip iterations because you can see where it is going. The marks are in the intermediate rows.
Trace your own programs too, before deciding they work. It is how you find the off-by-one error that would otherwise cost you the question.
Preparing without a computer
Most of this paper is reachable with paper alone, which is fortunate because many candidates have limited machine time.
- Write programs on paper from past questions — exactly what the exam requires.
- Trace them by hand to check them. This replaces the compiler and is a marked skill in its own right.
- Keep a pattern notebook — one page per structure, written from memory, tested weekly.
- Use machine time for verification, not for learning. Type up what you already wrote on paper and see where it fails.
The past papers library supplies the questions, and the offline study guide covers building a local library in one connected session.
In the exam
Read the whole question before writing — later parts often constrain how the earlier ones should be structured. Watch the marks rather than the questions when allocating time.
And if a program will not come, write what you can: the declarations, the input section, the loop structure with a comment saying what belongs inside. Method marks are real and a blank space is the only guaranteed zero. Partial code that shows a correct approach frequently earns most of the available marks.
Frequently asked questions
Which language should I use?
The one your syllabus specifies. Where there is a choice, use the one you can write fluently from memory.
Do I lose marks for syntax errors on paper?
Minor slips are usually tolerated; structural errors are not. Correct logic with a small syntax mistake generally scores well.
How much should I comment?
Enough to show intent at the non-obvious steps. Commenting every line wastes time you need.
Can I prepare without regular computer access?
Yes, for most of the paper. Writing and tracing on paper is exactly what is examined.
How many past papers should I do?
Fewer, fully written and traced, beats many skimmed. Ten complete papers written by hand is a serious programme.
