How to Revise for a Programming Exam in 7 Days

One week to your programming exam, you haven't opened the lecture slides since week 6, and you're panicking. Good news: a programming exam is more reviseable than most students think, because it's mostly applied rather than memorised. The plan below is what I give every student in this exact situation.

This works for CS1010, CS2030S, CS2040S, CZ1003, IS200, and basically every introductory and intermediate programming module in Singapore.

Day 1, Inventory

Before you study anything, list:

1. Every topic on the syllabus, from the module page or lecture notes.
2. Your confidence level on each (1-5).
3. The format of the exam: closed book or open, MCQ or written, time allowed, what tools.
4. The number of past year papers available.

Take the bottom-third confidence topics and write them on a single page. That's your focus list. The top-third you barely touch this week. The middle-third you skim.

Most students study the topics they already know because it feels productive. Do the opposite.

Day 2, Past papers, in order

Find every past year paper you can. Set them in chronological order, oldest first. Pick the oldest one. Sit down, set a timer for the actual exam length, and attempt it from scratch.

Don't look at solutions yet. If you don't know an answer, write down what you tried and move on.

When the timer ends, mark yourself honestly. Note which topics you got wrong. Add them to your focus list from Day 1.

The point of Day 2 isn't the score. It's to calibrate. By the end of today you know roughly where you stand and what you need to fix.

Day 3, Top 3 weak topics, deep

Pick the three weakest topics from Day 1 + 2. Spend the whole day on them. For each:

1. Re-watch the relevant lectures at 1.5x speed (you remember more than you think).
2. Re-do every tutorial problem from those weeks without looking at solutions first.
3. Find one or two related past paper questions and solve them.

If you're still confused after this, that topic is not going to suddenly click in the next 4 days. Better to focus on getting the medium-confidence topics to high-confidence than to keep grinding the hopeless ones.

Day 4, Past paper #2, then targeted practice

Same routine as Day 2. Sit a different past paper under timed conditions. Mark yourself.

You should see a small improvement. If you don't, you're reviewing without practising. Stop reading and start solving.

Spend the afternoon on one specific weak topic, doing as many problems as you can fit in. Quality matters less than reps at this stage.

Day 5, Cheat sheet (mental, even if not allowed)

Even if your exam is closed book, build a mental cheat sheet. On one piece of paper write:

• The 5 most common patterns you'll need (e.g. "loop with index", "two-pointer", "dictionary lookup")
• The syntax that you keep forgetting
• The complexity of the main data structures
• The 3 hardest concepts and a one-line summary of each

Try to fit it on one A4 page. The act of compressing forces you to choose what is important. Look at it before bed and again in the morning. By exam day the contents are in your head.

If your exam is open book, build the same sheet but more thorough. You'll refer to it during the exam.

Day 6, Past paper #3, then rest

Sit one more past paper. By now you should be scoring noticeably better. Mark yourself, note any remaining weak topics.

In the afternoon, rest. No code. No revision. Sleep early. Don't pull an all-nighter the day before, you'll perform worse.

If you have a topic that's still completely broken, accept it. Spend 30 minutes seeing if you can score any partial credit, then move on. Trying to learn something new the day before the exam costs you more in performance loss than you gain in coverage.

Day 7, Light warm-up, then exam

Morning of the exam:

1. Wake up early enough to be alert without being rushed.
2. Eat normally. Big breakfast or no breakfast, whatever your default is. Don't change today.
3. Skim your cheat sheet and re-do one easy problem to warm up. The goal is to be in "code mode" mentally.
4. Don't read new content.

Walk in at least 15 minutes early. Bring more pencils than you need, water, and your IC.

During the exam

The single biggest grade booster is time management.

• Spend the first 5 minutes reading every question. Mark difficulty, decide order.
• Do the easy questions first. Bank the points.
• For each question, write down what you're going to do before you write the answer. A quick comment with the algorithm steps protects you from forgetting halfway.
• If a question stalls for 10 minutes, move on. Come back at the end.

The students who fail badly are usually the ones who got stuck on question 3 and didn't even attempt 4 and 5. The students who do well are the ones who did 1, 2, 4, 5, easy parts of 6, then came back to 3.

If the list looks impossible

Day 1 done and the focus list is overwhelming, drop me a Telegram with the module you're taking. A focused two-hour session can compress a week of solo revision, past papers walked through together, with what to study and what to drop called out plainly.

Reading week and exam periods get busy on my end too, so book early. Three days out and you haven't started, ask anyway. Partial preparation beats panic.

What to do after the exam

Whether it went well or badly:

1. Forget about it for 24 hours. Don't analyse the exam at the bar with classmates. It doesn't change the grade and makes you anxious.
2. Review the topics you got wrong when grades come back. Even if you passed, those gaps will haunt you in the next module.
3. Don't panic-RTU yet even if you think you failed. Wait for grades. Singapore exams often grade more generously than feared.

Programming exams reward calm, methodical work. Practice that now, panic later.