Bytes and Words

Who I Am

I’m a Principal Technical Partner at Thoughtworks. Over the last decade I’ve helped large enterprises with legacy systems — sometimes that means untangling years of accumulated debt and rebuilding it into something teams can move with; sometimes it means building entirely new capabilities alongside the legacy so the business can move faster without waiting for a rewrite that may never come.

The last few years have shifted toward platform engineering and engineering effectiveness: the infrastructure, practices, and culture that let engineering organizations scale without grinding to a halt.

Right now my focus is on what AI-assisted coding and agentic platforms mean for how software gets built — and how they can rewire critical business workflows for organizations willing to rethink how work gets done.

Why “Bytes and Words”

Software is made of bytes — the compiled artefacts, the bits on disk, the instructions the CPU executes. But the craft lives in words: the design doc that aligns a team, the commit message that explains why, the conversation that unsticks a hard problem, the post that turns a half-formed idea into something transmissible.

The name also reflects how I plan to organize the writing here. Bytes are short technical notes — the kind of thing that used to fit in a tweet. Words are mid-length essays: a single idea, worked through without needing sections or a table of contents. Memories are long-form pieces — the full treatment, with structure, references, and a ToC.

What I Write About

Contact