From Kitty Hawk to the Moon.
And Far Beyond.
Sixty six years separate the Wright brothers from Apollo 11. Today's cycles compress a comparable arc into a single decade. The durable skill is learning to work with that pace of change.
Milestones That Reshaped Everything
Each of these shifted what was possible. Notice how the gaps shrink.
Wright Brothers
Twelve seconds at Kitty Hawk. Powered flight becomes possible and the next 66 years end on the Moon.
The Transistor
Bell Labs builds the device that makes every later computer cheap, small and reliable.
Apollo 11
From dirt strip to lunar surface in two generations. The proof that compounding works on civilisational timescales.
The Microprocessor
Intel 4004 puts a computer on a single chip. Moore's law starts compounding visibly in the consumer's hand.
Commodore 64
A computer in the living room. For a whole generation of engineers, this is where personal computing began.
World Wide Web
Tim Berners-Lee publishes the first web page. Information stops being scarce. Every business now has a software problem.
AWS / Public Cloud
Compute, storage and bandwidth become utility metered services. Infrastructure stops being a moat for most companies.
iPhone / Mobile First
A general purpose computer with sensors, in every pocket. Every product becomes a connected product.
Kubernetes / Containers
Workloads become portable. The unit of deployment shifts from server to container, and infrastructure becomes truly programmable.
Attention Is All You Need
The Transformer paper. In hindsight, the moment the modern AI wave became inevitable, even if almost nobody knew it yet.
ChatGPT / LLMs Go Mainstream
Natural language becomes a programming interface. The fastest consumer adoption in tech history.
Agentic AI
Models move beyond chat. They take actions across several steps, call tools and operate real systems.
What Comes Next
Self improving systems, hybrid workflows that pair people with agents, and architectures that absorb capability shifts without rebuilds. The cycle keeps tightening.
From Bare Metal to Agentic AI
Our practice is grounded in the bare metal tradition: understanding systems from the hardware up, with no abstraction to hide behind. That discipline never went away. It keeps finding new ground to work on.
The disciplines of that era, operating systems understood end to end and networks built and debugged by hand, remain the foundation of how we engineer today.
Then came virtualisation, public cloud, containers and orchestration. Each one rewrote what "infrastructure" meant, and each time the engineers who treated the previous wave as permanent were left behind. The ones who treated it as a tool kept moving.
Today we build with LLMs the way we once built with shell scripts: as primitives that compose, that need supervision and that need observability. The tools are new and the discipline is the same.
Systems engineering from the hardware up, when the hardware was the API.
Architected and operated cloud native infrastructure as soon as cloud native was a phrase worth saying.
Kubernetes at scale, GitOps workflows, internal platforms, the layer that turned ops into a software discipline.
LLMs and autonomous agents in production. Treating them like any other tool: powerful, fallible, in need of guardrails.
Riding Change Is a Skill,
Not Luck.
The engineers who stay relevant across several waves are not smarter than the rest. They have specific habits, and those habits can be learned.
Nobody needs to predict the future. What matters is recognising when the curve is bending under you and being able to respond while it still counts.
Pattern Recognition
Spot the structural similarities between yesterday's shift and today's. Cloud taught lessons that apply directly to AI.
Curiosity as Default
Try the new tool, read the source and build a small version of it. Curiosity compounds.
Discard Sunk Costs
Your existing skill stack is not an entitlement. Let it go gracefully when the next layer makes more sense.
Bet on Adoption Curves
Not every new technology matters. The ones that compound across industries do, and telling them apart is a skill.
Here to Help You Ride It
Two decades of working through these waves directly have shown us how most of the wrong calls happen and how to avoid them. The aim is to be well positioned for the next one, whatever it turns out to be.
Tech Strategy Mentoring
Calibrate your roadmap to where the curve is bending. We work through what to invest in, what to defer and what to retire.
AI Adoption Guidance
Pick the right level of integration for your team. Avoid the trap of either overcorrecting or pretending the wave doesn't exist.
Architecture Future Proofing
Design today's systems so tomorrow's primitives can plug in without a rewrite. Boring interfaces, replaceable internals.
Ready to map the next wave?
Let's chart it together.
A focused conversation about where your stack is today, where it is heading and what to do first.
Book a Discovery Call