Review mistakes in a way that changes next time

A mistake log is only useful if it changes what you do on the next problem.

Use this post as a small study note for making better decisions while solving, not as a quick definition dump. Read the idea, pause at the example and try to move one line forward yourself, then use the checklist on a real problem.

The main idea

For each missed question, write what you thought, what the correct trigger was, and what you will do next time.

The important part is not memorizing the method; it is noticing what calls the method into action. Which expression, diagram, unit, variable, or code behavior made this approach the right one? If you can name that trigger, a similar problem becomes much less stressful.

A short example

If you used total speed instead of vertical component, the next-time rule is: draw components before any kinematics equation.

How to approach it step by step

1. Write the givens cleanly and fix units, symbols, or variable names before calculating.
2. Identify the intermediate fact you need before trying to jump directly to the answer.
3. After each line, run a small check: do the units match, is the sign correct, is indentation or scope correct in code?
4. When you get an answer, return to the original question and check that it answers exactly what was asked.

Check while you solve

• Name the exact wrong move.
• Name the clue you missed.
• Write a next-time rule in one sentence.

The common mistake

Do not write 'be careful' as a fix. It is too vague to guide your future self.

The practical way to catch this mistake is to check the decision points, not only the final answer. Ask questions like: Why this formula? Why this component? Why this loop condition? That makes the answer stronger in content, not just in arithmetic.