Recommended resources
The freely available resources this lesson will direct you to.
Hello! Last lesson, you completed a timed, closed-book attempt and annotated wrong, incomplete, or uncertain answers with their likely causes. Keep those original answers nearby. Today you’ll turn the annotations into an error log that tells you what to revise, when to revisit it, and how to tell whether the weakness has improved.
This is part of the exam-preparation system you’re building alongside your computer science degree. Allow about 40 minutes to read, set up the log, and plan the first revision slots. The revision sessions you schedule will happen later.
Build a log you can act on
An error log is more useful than a list of wrong answers because it preserves the connection between a mistake and its remedy. The University of North Carolina Learning Center’s Test Analyzer offers a starting point: record the question, its type, why it went wrong, and where the relevant material can be found.
Test Analyzer: Exam Review Self-Reflection
Read the University of North Carolina Learning Center’s exam-item analysis to see how a short record can connect each mistake to a cause and a course source.
In “Exam Item Analysis,” begin with the sentence asking you to explain why each question went wrong. Read the reasons and table, then look over the blank rows beneath the four column headings. Focus on what you would need to add to that table to make it useful for scheduling a retest.
Use one row per question or distinct error, not one row for every incorrect line of working. Your version needs a few extra fields so that an observation becomes a plan:
| Question and topic | Cause and evidence | Correct idea and source | Next action | Retest and result |
|---|---|---|---|---|
| Binary-search trace, Q3 | Procedural step: narrowed the interval correctly, then reused its old midpoint | Recalculate the midpoint from the current bounds; check the course’s trace example | Trace two new arrays without notes | Tomorrow: pending |
Keep entries brief but specific. “Careless” is hard to act on; “reused the old midpoint after changing the bounds” tells you exactly what to practise. A source can be a lecture slide, textbook section, verified solution, or your corrected revision sheet. If you cannot verify the correction, mark the entry unresolved and seek a reliable course source before rehearsing it.
Your previous annotations already supply much of this information. Transferring them should take about 10 minutes; you do not need to rewrite every answer. Log uncertain correct answers too if you could not explain them without guessing.
Find the pattern beneath the mistakes
A single error identifies something to check. A recurring mistake is stronger evidence that your current way of studying or answering needs to change. Look across practice attempts, quizzes, and returned work for repeated combinations of topic and cause. Two wrong answers caused by the same overlooked condition in separate questions are more informative than two wrong steps within one question.
The University of Michigan’s Final Preparation for the Exam stresses that noticing a repeated “silly” mistake is not enough: redo the work correctly. It also recommends examining whether particular kinds of wording repeatedly cause trouble.
Final Preparation for the Exam – Study Skills
Read the University of Michigan’s advice on recurring errors to distinguish recognizing a pattern from actually practising a better response.
Under “Analyzing your mistakes,” start at the paragraph about an exam that seemed to be going well. Read the analysis advice through the end of the second bullet. Notice the different remedies for a repeated missing step and a repeated misreading of qualifiers.
Group log entries only when they point to the same remedy. For instance, repeatedly failing to explain why binary search requires sorted data suggests a concept gap. Repeatedly choosing the correct search interval but calculating the next midpoint from outdated bounds suggests a procedural-step problem. Both concern binary search, but rereading the definition will not adequately fix the second problem.
The cause labels from last lesson can guide your next action:
| Primary cause | Targeted revision |
|---|---|
| Concept gap | Relearn the condition or idea from a verified source, explain it from memory, then apply it to a new case. |
| Wrong application or category | Compare two question types and practise deciding which method fits before solving. |
| Procedural step | Redo the sequence correctly, then complete fresh examples while checking the step you tend to miss. |
| Reading omission | Mark qualifiers or separate parts of new prompts before answering; check that each part is addressed. |
| Time issue | First rule out a hidden knowledge gap. If pace is the issue, practise a small mixed set under an appropriate time limit. |
Spend a few minutes marking repeated patterns in your log. If you only have the short attempt from last lesson, label a suspected pattern provisional rather than claiming it recurs. Later attempts will provide better evidence.
Give each priority a revision slot
The log now answers what needs work. To decide when, bring back your subject-priority matrix from earlier in the module. Consider the assessment’s weight and proximity, alongside how uncertain you remain. Within a high-priority subject, give an early slot to an unresolved concept needed for many questions or to a recurring error; do not spend that slot polishing answers you can already produce reliably.
A scheduled entry should name a time, action, and check. “Revise algorithms” is too broad. “Tuesday, 20 minutes: explain binary search’s sorted-input requirement without notes, then solve two unfamiliar applicability questions” is something you can do and assess. Reserve realistic blocks around classes and startup responsibilities rather than assuming an uninterrupted day.
Here is one possible sequence when an assessment is still several days away:
- Today: Verify the correction and redo the original question so you understand the sound solution.
- Next available day: Attempt a new question on the same weakness without notes. Record whether you could explain and apply the idea.
- A few days later: Retest with another new question, preferably worded differently or mixed with other topics.
- Before the assessment: Give still-active weaknesses another short check. Spend less time on entries that have held up across independent retests.
These intervals are a planning example, not fixed rules. If the exam is tomorrow, move the most important checks into the time available; if it is weeks away, spread them out. For the next eight minutes, place your highest-priority one or two patterns into actual calendar slots. A small number of protected slots is better than a long list you cannot complete.
Let retest results change the plan
The final column of the log should record more than “reviewed.” After each scheduled check, note the date, whether the question was new and closed-book, and what happened. A correct answer reached by looking at the solution is a useful review, but it is not evidence that you can retrieve the method independently.
If a new question exposes the same error, keep the entry active. Reconsider the cause: a “procedural” mistake that survives repeated traces may conceal a misunderstanding of what the bounds mean. Change the remedy if the evidence changes. If you can explain the idea and solve a couple of independent variations without help, lower its priority rather than repeatedly revising it for comfort.
This makes the log a small feedback system: your next study block responds to demonstrated weaknesses, and each retest supplies evidence for the following decision. It also keeps revision proportionate to the assessment instead of letting familiar material consume the time available.
Takeaway
Your error log should connect a specific error, evidence of its cause, a verified correction, a targeted action, and a dated retest. Watch for patterns across independent questions, schedule the most consequential weaknesses first, and update the plan from closed-book results.
In the next lesson, you’ll build a flexible weekly study plan that protects these exam-preparation slots while leaving small, deliberate blocks for portfolio work.