Waitlist openJoin the waitlist

For structural engineers, 2–15 years in

Be the engineer
everyoneno one brings the hard problem to.

Not the one who runs the model. The one who sees the load path, knows which clause is lying, and can convince a room.

Analysis is cheap now. Judgement is the rare skill — it has only ever come from reps you had to be lucky to receive. The right project, the right supervisor, the right decade. I've built the place you can get them on purpose.

Hundreds of hand calculations, sketches and real anonymised details, marked against rubrics written by practising engineers.

You'll pay less than everyone after you — I haven't set the number yet, but the list gets it first and gets it lower. And I'll ask what you want built: the first cohort shapes the curriculum.

Sheet 1 of 5General arrangement

Nobody gets enough reps anymore.

Judgement was never really taught, it was absorbed from the work and the people around you — from seeing enough of it. It was always a lottery. The right project, the right supervisor and the right few years. Get those and you came out the other side on a fast track to mastery.

Miss them? You’re ten years in with only five years of reps. It’s not your fault you spent two years on condition assessments in a slow market, or three years on a project where nobody has time to explain anything. The hours you would have spent working something out properly went to the program or fee.

You can’t practise a thing you don’t get to do.

Sheet 2 of 5The problem

You can already design a beam.

You can size it, reinforce it, check it and issue it. This course is about whether you understand it.

Nothing here is a lecture series. Every unit is run as the same five moves, in the same order, on progressively less forgiving problems.

The shape of every unit in the spine

  1. 01

    Derive the behaviour from statics and physics.

    No code, no software. Where does the equation come from, and what assumptions are sitting underneath it?

  2. 02

    Feel a set of rapid qualitative calls.

    Sketch the bending moment diagram. Which of these three details is stiffer? Where does this crack? Thirty seconds, then you get told why.

  3. 03

    Calculate by hand, spreadsheet or code.

    Uploaded and graded on method and presentation, not just on whether the number came out right.

  4. 04

    Explain the result to somebody who matters.

    Three formats rotate: a sketch a detailer could build from, a paragraph a client could follow, a defence of your assumption to a reviewer who disagrees.

  5. 05

    Judge with too little information.

    Scenarios with competing constraints and a gap in the brief. What do you do — and what do you tell the client you don’t know?

Five moves. Repeated eleven times, on less forgiving each pass.

The spine

2 parts · 11 units

  1. Part one

    Fundamentals

    The behaviour, the material and the members. Seven units, each run through the same five moves.

    1. 01Structural behaviourLoad goes where the stiffness is, which is why the member you stiffened to fix a deflection now has moment you did not design it for. Equilibrium is non-negotiable, compatibility is where the assumptions hide, and redistribution is the structure quietly disagreeing with your model.
    2. 02Finding the load pathStrut and tie as the general method rather than just the thing you reach for at a corbel or a nib. Thrust lines are how arches were sized for two centuries without a single stiffness matrix, and they still tell you in thirty seconds whether a scheme wants to work.
    3. 03Concrete behaviourCracking, creep, shrinkage and redistribution — every one of them time-dependent, and every one of them the reason the structure you check at 28 days is not the structure that exists at year forty. Restraint cracks nobody calculated, and locked-in forces nobody drew.
    4. 04BeamsFlexure, shear and torsion, derived rather than looked up — where the lever arm actually comes from, why shear is the one that gives no warning, and why you can design out torsion.
    5. 05ColumnsSlenderness is a stability problem wearing a strength problems clothes, and the effective length you assume does more to the answer than the concrete grade you specify. Second-order effects, when the moment magnifier is hiding a scheme that should have been braced.
    6. 06DetailingAnchorage, laps and congestion — the half of design where the calculation is already finished and the drawing decides whether it works. Whether the bars physically fit, whether a vibrator can get in, and whether the steelfixer will build what you drew or what is easier.
    7. 07PrestressCompression you choose to put there, and a tendon profile worked backwards from where you want it. Losses that are simple to compute and simple to get wrong, and a structure that behaves differently the day after transfer than it does at year forty.

  2. Part two

    Decisions

    Everything above, used under real conditions — where the answer is a judgement you sign, not a number you check. Four pillars, run through the same five moves.

    1. 08Sizing membersApproximate methods, span-to-depth, order-of-magnitude. The number you should already expect before you press go.
    2. 09Interrogating modelsWhat would tell you the analysis is wrong. Which assumptions the software made on your behalf, and whether you agree with them. The hand check that would have caught it.
    3. 10Choosing schemesWorking from a brief that is incomplete or wrong. Generating more than one option. Comparing schemes on cost, buildability, programme, durability and carbon rather than on material efficiency alone. Knowing when you have done enough work to choose — and committing.
    4. 11Owning decisionsDesign review, given and received — including how to be reviewed without defensiveness, which is a skill nobody teaches. Communicating value upstream to clients and contractors. What you are actually signing, and what risk you have taken on. Failure cases worked as decisions made with the information available at the time, not as hindsight narratives.
Sheet 3 of 5Curriculum

Who am I?

I've been designing bridges for eleven years.

Luke WeatherstoneLuke WeatherstoneBridge engineer / software ·

Eleven years on projects like Sydney Gateway, the M7/M12 Interchange and the Commonwealth Avenue Bridge Renewal — alongside tender work, proof engineering, design reviews, load ratings and strengthening jobs.

And a lot of mentoring, which is where this began. The engineer I remember most had six years in and could not size a beam without opening the software. Not because she was not good — she was very good — but nobody had ever made her do it by hand enough times for it to stick, and by then it was awkward to admit. She was one project away from being excellent and nobody was going to give her that project.

There was a detour early on. I left engineering for a couple of years and ran a martial arts gym full time, because I could not see the point of what I was working on. I came back because I found it again. The gym is where this whole thing clicked. Nobody in a gym believes you can explain a skill into somebody.

Capability is not explained into people.
It is drilled in.

Structural engineering is no different. So the curriculum is built around reps on real, anonymised details rather than lectures — and I have built the thing that delivers them myself, the same way I have built section analysis software and taught myself to program.

It is also too important to be one person's view of the world. A panel of experienced practitioners across specialisations is being assembled to write and stress-test the material.

Sheet 4 of 5Who am I?

Stop running the numbers.
Start making the call.

The engineers everyone brings the hard problem to were not born that way. They got the reps.

You'll pay less than everyone after you — I haven't set the number yet, but the list gets it first and gets it lower. And I'll ask what you want built: the first cohort shapes the curriculum.

Sheet 5 of 5Issued for construction