A single worn pencil and an eraser resting on a ruled notebook turned at an angle, lit by a desk lamp with a dark window behind

Getting better at physics comes from what happens inside each problem, not from the number of problems. Attempt every one before looking at any solution, work in symbols until the last line, check the answer by its features rather than against the back of the book, and practice the step you keep getting wrong on its own.

More problems help only if each one is exercising the right thing. A student who works forty problems by matching them to worked examples has practiced matching forty times. A student who works ten, and on each one chooses the principle, carries the algebra, and checks the result without help, has practiced physics ten times. The second student has practiced the thing the course tests, and the reason is not effort. It is what the effort was spent on.

This post is about that second kind of practice. If the problem is the schedule, the reading or the lecture-to-homework gap, the companion post on how to study physics covers those.

How do you get better at physics if doing more problems is not the answer?

By changing what you do with the problems you already have. A physics course at UC Davis puts the diagnosis bluntly in its introduction on how to learn physics: students who try to do as many different practice problems as they can, hoping to collect every “trick,” are using an approach that fails in a class that tests understanding. The same page says practice problems are helpful, but the emphasis should be on how they are the same, not on how they are different.

That reframes the whole job. The goal is not to have seen the exam problem before. It is to recognize that the unfamiliar problem in front of you is a situation you already know, wearing a different costume: a block on a ramp that is really Newton’s second law along one axis, a swinging ball that is really conservation of energy.

OpenStax’s problem-solving chapter makes the same point from the other side. It argues that the ability to apply broad principles to specific situations is much more powerful than memorizing a list of facts, because no list can be long enough to cover every circumstance.

Why should you attempt a problem before looking at the solution?

Because following a solution feels like learning and mostly is not. The UC Davis page compares it to having a weight lifted for you and then handed over to hold: it feels like something, but it does not build the muscle. Its advice is to avoid looking at solutions as much as possible, and it adds that even an attempt that fails teaches more than skipping straight to the answer.

The practical version: cover the solution, attempt the whole problem, and only then uncover it. If you get stuck, uncover one line, not the whole thing, and continue on your own from there. OpenStax suggests the same habit for the book’s own examples, which it recommends working out for yourself as you read. A worked example you have attempted first is worth several you have only read.

What does working in symbols buy you?

The ability to check your answer. Oberlin College’s physics department recommends working problems with symbols and substituting numbers only at the very end, and gives three reasons: symbols are easier to manipulate than values like 2.59 kg, intermediate quantities often cancel, and, most important, a result written as an equation can be examined in ways a bare number cannot.

That third reason is the one that makes you better. A number such as 2.45 m/s² tells you nothing about whether it is right. The equation that produced it, for two masses hanging over a pulley, is a = (m₂ - m₁)g / (m₁ + m₂), from Newton’s second law applied to each mass, and that can be interrogated. The same page also suggests naming symbols after what they stand for (m_h for a helium atom, m_g for a gold atom) rather than m₁ and m₂, which is a small habit that prevents a surprising number of swapped variables.

How do you check an answer without the back of the book?

By comparing its features with the features you expect. Oberlin’s page says checking an answer does not mean comparing it with the answer in the back of the book, and lists what to compare instead. Four of them are worth turning into habits.

Units. Every term in a result must reduce to the unit you want. Take the position equation from the kinematics equations, x = v₀t + ½at². The first term has units (m/s)(s) = m and the second (m/s²)(s²) = m, so it passes. Now suppose a rushed derivation produced v = √(2g/h). The units are √((m/s²)/m) = √(1/s²) = 1/s, which is not a speed, so the formula is wrong before a single number goes in. The correct result, v = √(2gh), gives √((m/s²)(m)) = √(m²/s²) = m/s.

Limiting cases. Push a variable to an extreme where you already know the answer. For the pulley result above, set m₁ = m₂: the numerator is zero, so a = 0, and two equal masses should balance. Set m₁ = 0: a = m₂g / m₂ = g, and a single mass with nothing on the other side should fall freely. Both limits come out right, which is strong evidence the formula is right too. Oberlin gives the same kind of test for a projectile’s range, which must be zero for a vertical launch.

Symmetry. If a problem has two objects, the answer should not depend on which one you called object 1. Swap the labels in the pulley result and a changes sign only, which just means the other mass now goes down. That is correct.

Reasonable size. Oberlin offers a quick conversion for speeds: double a value in m/s to get a rough figure in miles per hour. A car’s maximum speed on a flat curve that comes out as 17 m/s is about 34 mi/h by that rule, which is plausible. A result of 170 m/s would be roughly 340 mi/h by the same rule, and you would know to go looking for the slipped decimal.

Why estimate before you calculate?

Because an estimate gives you something to check against. OpenStax describes estimation not as guessing but as using prior experience and sound physical reasoning to get a rough idea of a quantity, and notes that estimates let you run sanity checks on calculations and rule out unrealistic numbers.

Thirty seconds is enough. Before working a problem about a dropped object, decide whether the answer should be closer to 1 m/s, 10 m/s or 100 m/s. After working it, compare. When the two disagree by a factor of ten, one of them is wrong, and finding out which teaches you more than a correct answer that you never questioned.

What should you practice on its own?

The step that keeps going wrong. The UC Davis page borrows the idea of deliberate practice from athletic training, where improvement comes from drilling the component parts of a skill rather than repeating the whole thing. Its example is the free body diagram: most students spend a short time learning to draw one and move on before mastering it, then jump straight to equations and get things wrong. The page’s instruction is to spend time getting good at such tools without regard to whether you solve the particular problem.

So pick the step. If your force problems go wrong, spend a session drawing only diagrams, ten of them, with no equations at all, and check each against the free body diagram rules. If your energy problems go wrong, spend a session only deciding, for each problem, whether mechanical energy is conserved and why. A set like the five practice problems is useful for this, because each one turns on a different condition.

Keep a short list of your own errors grouped by type (wrong principle, missing force, sign, units, algebra). After a few weeks the list usually shows that most of your lost points come from one or two categories, and those are the categories worth drilling.

When does another explanation help, and when does it not?

Another explanation of someone else’s example rarely helps; you have already followed several. What helps is seeing where your own attempt went wrong. That is the one moment in this process where Electra is useful: photograph the problem you attempted, compare your work with its step-by-step solution, and ask about the exact line where the two diverge. Every step is shown so you can find the difference yourself rather than copy a result.

So what changes on Monday?

Three things. Cover every solution until you have attempted the problem. Carry symbols to the last line and run the unit and limiting-case checks before you look up any answer. And spend one session a week on your weakest single step instead of on a new problem set.

None of it adds problems to your week. It changes what each one teaches you. The problem-solving method puts these checks into a fixed sequence, and the formula pages state the condition behind each equation, which is what most limiting-case checks end up testing.

Sources