Read textbooks with a pencil, not a highlighter-first mindset

Highlighting can mark importance, but it does not prove understanding. A pencil can make you interact with the page.

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

After each paragraph, write a margin question or draw the relationship the paragraph describes.

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

For a physics derivation, label what each variable means and why the next line follows.

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

• Turn headings into questions.
• Rewrite one key sentence in your own words.
• Do the sample problem before reading the solution.

The common mistake

If a paragraph cannot become a question, you probably have not found its job yet.

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.