Memory safety without a garbage collector turned out to be a bigger deal than anyone expected. This is the story of how a small shift in perspective changed the way we approach why rust is quietly taking over systems programming, and why it might change yours too.

The best practitioners share a habit that is easy to miss: they make their work legible. They leave a trail of decisions, so that six months later a stranger — often their future self — can understand not just what was done, but why.

Why this matters now

Constraints are not the enemy of creativity; they are its engine. Give someone infinite options and they freeze. Give them a tight box and a deadline, and something interesting almost always crawls out.

None of this is free. Every choice buys you something and costs you something else, and pretending otherwise is how teams end up surprised by consequences they were warned about in advance.

The goal was never to do more things. It was to do the right things, and to notice the difference.

The part nobody tells you

It helps to zoom out. The specific tools will change — they always do — but the underlying shape of the problem tends to rhyme across decades. Learn the shape and the tools become interchangeable.

• Optimise for the feedback loop, not the first draft.
• Write things down; memory is a liar with good intentions.
• Prefer boring, reversible decisions early on.
• Measure the thing you actually care about, not its proxy.

Where to start

What surprised us most was how much of the gain came from subtraction. We did not add a clever new process; we removed three old ones that no longer earned their keep.

For years the conventional wisdom went unchallenged, repeated in conference talks and posts until it hardened into fact. But conventional wisdom has a short shelf life, and the ground has shifted under our feet more than once.

If you take one thing away, let it be this: the fundamentals are unfashionable precisely because they work. Master them, and the trends will take care of themselves.