LC Computer Science exam-day guide

Stop learning new content and start converting knowledge into marks. Sit at least one full paper under real conditions: timed, on paper, no IDE, no notes, phone away. Mark it honestly against the scheme and list the topics where you lost marks rather than the topics you enjoy. Then drill the highest-yield hand skills, because these are what the written paper actually tests: tracing a loop with a trace table, dry-running a recursive function, converting between binary and decimal, writing a short program with input validation, and explaining a searching or sorting algorithm step by step. Also rehearse the long-form answers - a design question, an ethics or societal-impact question - because they are marked on structure and specific reasoning, not on length. Two focused sessions a day beats one long unfocused one.

Switch to consolidation only. Re-read your one-page summary and your own list of mistakes from the practice paper, then close the books. Pack the bag now, not in the morning: pens and spares, pencil, eraser, ruler, clear pencil case, watch, water, candidate number, timetable. Check the venue, the start time and the travel plan one final time, including whether your centre has changed room. Decide what happens to your phone. Eat properly, avoid an all-night session, and set two alarms. If a topic still feels opaque at this point, write down the two or three facts you do know about it and move on - cramming a new topic in the last evening usually displaces things you already had.

Eat breakfast and hydrate; a two-and-a-half-hour written paper is a stamina event. Arrive early with the buffer you planned, and use the waiting time for a calm skim of the summary sheet - not for a panicked attempt to learn something new. Hand up or leave your phone as arranged before you enter the building, and check you still have your pens and candidate number. Once seated, fill in the details on the script carefully and completely, then use any remaining minutes to read the front cover: number of questions, mark allocation, and any instruction you might otherwise skim past. Breathe, and treat the first question as a warm-up rather than a test of your worth.

Spend the first few minutes reading the whole paper and marking each question with its marks. Convert marks into minutes - a common rule of thumb is roughly a minute per mark, adjusted to whatever the paper states - and write your target finish time for each section on the corner of the script. Start with the question you are most confident in to settle yourself, but do not overrun: when the time for a section is up, move on and come back only if there is slack. On programming questions, state the language you are writing in, comment your code, validate input, handle the edge case you were given, and keep indentation consistent - examiners read for structure as well as logic. On tracing questions, draw a proper table with a column per variable and one row per iteration; do not do it in your head. On design, ethics and societal questions, take a position, give the specific reason, and name the concrete example. Attempt every part - there is nothing to gain by leaving a blank. Reserve the last ten minutes to check question numbering, that all pages are attached, and that no answer has been written in the wrong place.