Skip to content
SDB
A monochrome landscape: farmland and a village on one side of a stone bridge, industry and a modern city skyline on the other, with four people walking across.

Est. 199630 years in Information Technology

The Digital
Journey

Transforming ideas into innovative digital solutions with cutting-edge technology. Specialising in enterprise applications, cloud architecture, AI, and robotics.

30+

Years in practice

04

Disciplines

Enterprise

Scale of work

Guides

AI · Robotics · Cloud

Math

Proofs that travel

The premise

Every system I have built
was a bridge.

On one side, the way work has always been done. On the other, the way it could be done. The engineering is never really about the technology — it is about carrying people across without dropping what they depend on.

I have spent 30 years on that crossing: from green screens and client–server, through enterprise Java and integration, into cloud, data platforms and now AI. This is where I write it down — the decisions that held, the ones that did not, and what I would tell a younger engineer standing at the near end of the bridge.

01

Enterprise applications

Core systems that carry a business for a decade: domain modelling, integration contracts and the unglamorous discipline of data that stays correct under load.

02

Cloud & platforms

Landing zones across the major clouds, resilience and cost as design constraints — migrations judged by how much cheaper change became afterwards.

03

AI & robotics

Language models, agents and physical systems put to work — separating the capability that compounds from the demo that does not survive contact with production.

04

Mathematics that travels

Queueing, kinematics, statistics — the equations behind capacity, motion and evidence, written so they apply beyond any one stack or robot.

Selected writing

From the notebook

Long-form essays on architecture, delivery and the technologies currently rearranging the profession.

All writing
Latest
Technology3 min read

The honest case for AI in the enterprise

Most enterprise AI programmes fail for the same reason enterprise search failed in 2008: nobody owned the data. Here is what actually has to be true before a model earns a place in production.

Read essay →
Engineering3 min read

Six architecture decisions that aged well

Looking back across thirty years of systems, the choices I am still glad about have almost nothing in common technically — but they share a single quality: they kept the next decision cheap.

Read essay →

1996 to today

Thirty years, four frontiers

The tools were replaced roughly every seven years. The fundamentals never were.

  1. 1996 — 2002

    Client–server and hand-built ERP

    Green screens giving way to three-tier applications, and financial modules written module by module. Learning that a release is a promise, and that data outlives every framework built on top of it.

    • Oracle
    • Forms
    • PL/SQL
    • Unix
  2. 2002 — 2015

    Global delivery and integration

    Thirteen years of enterprise integration across four continents — middleware migrations, platform consolidations and the long education that the hard problem was never the code, it was the contracts between teams.

    • SOA
    • Fusion MW
    • OTM
    • Exadata
  3. 2015 — 2021

    Cloud and the modernisation years

    Lifting estates off the data-centre floor. Autonomous databases, IoT, pipelines and the discovery that architecture is mostly the art of making change cheap.

    • OCI
    • AWS
    • Azure
    • IoT
  4. 2021 — today

    AI platforms, agents and digital twins

    Model-led systems, knowledge graphs and retrieval built as governed enterprise platforms. The frontier moved again — and thirty years of fundamentals turned out to be exactly the right preparation.

    • LLMs
    • Agents
    • Graphs
    • Digital twins

The next crossing

If you are modernising something that matters, I am glad to compare notes.

Architecture reviews, cloud strategy, AI adoption, or simply an honest second opinion from someone who has seen this pattern before.