Architecture is the constant. Constraint is the material.
Twenty years of infrastructure, security, networks, and distributed systems have produced one reliable observation: the interesting problems are never technical. They are architectural — how parts interact under pressure, where failure accumulates before it surfaces, and where durable advantage can be designed into a system rather than assumed away.
Rebuilding without permission sits underneath the work. It comes from recovery, responsibility, and a practical refusal to wait for ideal conditions before building forward.
Two decades of operational depth across infrastructure, networks, security, and distributed systems.
- 2005 to 2010
Hosting, systems administration, FreeBSD and Linux estates, switching, firewalling, identity provisioning, and early architectural work. - 2010 to 2015
Network architecture across datacentres, carriers, rail, aviation, and enterprise environments, covering BGP, MPLS, QoS, migration design, vendor transitions, and large-scale operational change. - 2015 onwards
Architecture, security, automation, retained advisory work, solution engineering, API integrations, and event-driven systems.
The work spans Brocade, Juniper, Cisco, VMware, Active Directory, telecom integrations, security architecture, distributed environments, Kafka-based systems, and incident analysis. The continuity lies in practical design for environments in which errors compound quickly.
Interim technology leadership and applied systems work.
The current focus is interim technology leadership — CTO, CISO, and DPO engagements where the role requires someone who can step in quickly, read the system accurately, and make decisions that hold under scrutiny. The value is not the title but the operational depth behind it: two decades of building, breaking, and redesigning systems across industries and jurisdictions.
Alongside client work, I am building an operating stack around Abel. Under that sit Aible, the privacy-first AI company, and Aible Studios, the fast delivery arm for websites and execution. The initiatives page has the wider picture.
Useful systems make structure and trade-offs explicit.
- Clarity over simplification.
Exact language is operationally important. - Continuity over isolated output.
A system should remain coherent across time. - Constraint over theatre.
Useful systems understand their limits.
- Traceability over convenience.
Important actions should be reviewable. - Architecture over features.
Tools matter less than system shape. - Operational fit over broad appeal.
Not every system belongs in every environment.