Engineering fails at assumptions and scale, not at missing a definition on a flashcard.
You’ll surface what you assumed, stress orders of magnitude, and rehearse stakeholder and failure pressure.
Use AI for the part of engineering that's judgement, and know why its answers in this subject need checking more carefully than in most.
Know which methods suit a subject where being approximately right about the right thing beats being exactly right about the wrong one, and where the marks and t…
Find the assumptions you made without noticing, which is where your marks go and where real structures fail.
Know roughly what the answer should be before you calculate, which catches the errors that matter and that no amount of careful arithmetic will.
Draw how force, current or flow gets from where it enters to where it leaves, and find out whether you actually understand the system.
Play the component at the moment it fails and narrate what happens next, which teaches more about a system than knowing how it works.
Know which way things move and how fast when you change something, which is design intuition, and is what separates an engineer from someone who can evaluate a …
Find out what each rule in a standard was written in response to, which turns a document you comply with into one you understand.
Defend a design to the people who will pay for it, build it, maintain it and regulate it, which is the conversation engineering actually consists of and which c…
Find out where the marks in an engineering answer actually are, which is rarely where students put their effort.
Find out whether your engineering problem is a mechanics problem, a maths problem, or a units problem, because it's usually one of those three and they need dif…
Keep a log that turns a term of scattered lost marks into three or four habits, and that doubles as the beginning of professional practice.
Find out that the thing you're stuck on isn't the thing you're stuck on; it's something from two years ago that never quite landed.
Build a record of your own mistakes that tells you what to study, in what order, and that gets more valuable every week instead of less.
Draw your own diagram of something, have what's missing or misplaced identified, and find out which parts of your mental picture were never there.
Before you run it, look it up, or turn the page, say what you think will happen, and why.
Change one variable at a time and watch the shape move, until you can predict the movement before you see it.
Handle a demanding client, patient, or user in simulation, practising translation, boundary-setting, and requirement extraction under pressure, not just solving the technical problem in a vacuum.
Have the unstated premises in your own reasoning named, the things you're relying on without having noticed you decided them.
Have your work marked the way an examiner would mark it, strictly, against the scheme, with the marks you didn't get explained.
Understand why the current way of doing something looks the way it does, by finding out what it replaced and what was wrong with that.
Play the system or person at the moment it fails and narrate the cascade, so you learn failure as a process, not a moral punchline.