Study tips for engineering students: problem sets, labs and staying human

Engineering · 7 min read

By Raul Blanco · Updated 12 July 2026

Engineering has a reputation for being one hard degree. This is inaccurate. It is four degrees, maths, physics, programming and technical writing, all sharing a single timetable and politely refusing to coordinate their deadlines.

The workload is real, but most of the suffering comes from studying it like a lecture degree when it is actually a practice degree. The marks live in problems solved, reports written and units that survive scrutiny. Here is the system, in the order the term will throw things at you.

The problem sets are the course

Lectures in engineering are trailers. The problem set is the movie. You can attend everything, nod at every derivation and understand each step as it happens, and still freeze when a problem stands alone on a page with no derivation to nod along to.

So flip the priority: budget your week around problem sets and treat the lectures as preparation for them. Two focused hours on problems teach more than four hours of tidying notes, and the exam is, structurally, just another problem set with worse lighting.

Struggle first, peek second, redo blind

When a problem will not move, the temptation is to check the solution "just for the approach." Do it too early and the solution installs itself as a false memory of your own ability. The three-step version keeps the learning and loses the self-deception:

Give every problem twenty honest minutes before looking anything up. Then study the solution properly, close it, and redo the problem from a blank page. The redo is the step everyone skips and the step that does all the work. A copied solution feels finished, but it is really a loan.

Write the lab report the same day

Lab data has a half-life. The evening after the lab, you remember why reading six looked weird and what the demonstrator said about the calibration. By Sunday, you are a stranger interpreting a dead person's spreadsheet. Thirty minutes of same-day writing, just the method, results and anomalies while they are warm, converts a three-hour Sunday reconstruction into a one-hour write-up.

Book that half hour like it is part of the lab, because it is. This is the kind of small recurring block a weekly study schedule handles well.

Maths is a dependency, not a module you passed

Every engineering course quietly imports your first-year maths. When third-year control theory feels impossible, the real error is often two layers down in rusty complex numbers or a Laplace transform you last touched in exam week. Run maintenance: twenty minutes a week redoing old fundamentals, targeted at whatever your current course keeps assuming. Debugging your maths at the source beats reading the same control theory page five times and blaming the module.

Units and sanity checks are free marks

Every cohort has the story: someone calculates a bridge that weighs four grams, writes it down, moves on. Two habits stop it. Carry units through the whole calculation, because if the units of your answer are wrong, the answer is wrong, no exceptions. And before finishing any problem, ask whether the number is even plausible. A motor at 40 percent efficiency, maybe. At 4,000 percent, you have invented free energy and should probably mention it to someone.

Under exam pressure these checks feel like a luxury. They are the opposite: thirty seconds of checking regularly rescues marks that took ten minutes to earn.

Group projects without mutiny

Engineering group projects fail socially before they fail technically. The fix is boring and works: split the project by deliverables, not vibes. Every task gets a name and a date, visible to everyone, in one shared plan rather than a group chat where deadlines go to be forgotten. When the plan lives somewhere everyone can see, "I thought you were doing that" dies out as a genre. Keep your own slice broken into sitting-sized tasks in a student planner, and when the mental load spikes mid-project, a five-minute brain dump clears the queue.