How to actually learn engineering
Engineering is two disciplines braided: things that must work and mathematics that must hold. Courses often teach them in different rooms; the engine plans them in the same week — 45% building, 40% quantitative method — because each is what makes the other stick.
The method
Build progressively harder working things, and work the mathematics those things stand on until it holds without the example.
Problems and projects in the same week: derive it, size it, then build or model the thing and see whether it behaves.
Planned as a blend: building working things 45% · quantitative method 40% · design 15%.
Where it goes wrong
The theory lectures and the lab never seem to meet.
Plan them to meet: the engine schedules engineering as build and quantify in the same weeks — 45/40 — so the mathematics is sized against a thing that has to work.
One early slip cascades through an entire design calculation.
Worked solutions for every problem separate the two failures — wrong method versus fumbled execution — and only one of them needs more theory.
What mastery actually looks like
Not a grade — observable abilities. A plan should be able to say which of these it has evidence for:
- Can build — produces a working artefact for a stated problem.
- Can debug — traces a failure from the symptom to the cause.
- Can design — chooses a structure that survives changing requirements.
- Can read — explains why an unfamiliar design works.
Keeping it
Return to what you built — an artefact you extend is theory you keep.
Common questions
Is engineering closer to maths or to building?
Deliberately both: the engine plans it 45% build, 40% quantitative, 15% design. Studying either half alone produces the classic failure — theory that cannot size a beam, or builds that cannot be justified.
How do I study engineering theory so it sticks?
Attach it to an artefact: derive, size, then build or model. The engine's retention rule for build disciplines is to keep extending what exists.
What should practice look like?
Problem sets AND a running project in the same week — about half of engineering study time is doing, split between the two.
Engine values reviewed 2026-09-01. Related: programming, cybersecurity, a language.
Akiri turns this into your actual week: tell it your goal and your date, and it measures where you're starting from, builds the plan backwards from the deadline with this discipline's own rhythm, and rebuilds it as you go — in English, French, Spanish, Hindi or Chinese.