Platform foundations
Standards, SDKs, templates, service foundations, and platform capabilities that turn repeated complexity into reusable delivery paths.
I build the reusable systems, standards, and platform capabilities that help engineering teams move faster with less ambiguity and stronger control.
01Delivery-led architecture.
02Secure defaults.
03Reusable systems.
SYS / 01About
About
Strategic platform work, grounded in engineering reality.
I work across platform engineering, architecture, infrastructure, developer experience, and secure delivery, with a focus on making complex environments easier to reason about and safer to scale.
Governed autonomy
Secure defaults and clear control surfaces that reduce cognitive load without taking ownership away from engineering teams.
Enterprise connection
Practical architecture that links deployment paths, operating models, service ownership, governance, and business outcomes.
“If your users haven’t built something that surprised you, you probably didn’t build a platform.”
SYS / 02Focus
What I Focus On
Reusable capability for teams operating in complex environments.
Platform capability
Reusable foundations, templates, SDKs, and standards that reduce cognitive load for engineering teams.
Secure delivery
Secure defaults, governed autonomy, and delivery paths that make the right engineering choice the easiest one.
Practical architecture
Architecture that clarifies decisions, improves delivery, and connects execution to long-term organisational capability.
ARCH / 03Operating Model
Current Shape
Architecture that improves delivery, governance, and ownership.
My work sits where strategy meets implementation: the platform standard, the delivery workflow, the control surface, the service boundary, and the operating model that decides whether engineering can scale safely.
Architecture and operating models
Connecting day-to-day engineering execution with enterprise architecture, governance, ownership, and business outcomes.
Engineering systems
Internal platforms, CI/CD, SDKs, templates, paved roads, and developer self-service that scale beyond one team.
Infrastructure and secure delivery
Cloud foundations, secure defaults, delivery controls, telemetry, readiness practices, and cost-aware operations.
ARCH / 04Principles
Project Cognition
How I move from enterprise intent to sustainable delivery.
01 / Enterprise Architecture
Start with capability
Understand the organisational intent, operating model, constraints, governance, and business outcome before choosing the technical shape.
02 / Solution Architecture
Shape the system boundary
Translate capability into service boundaries, integration points, risk controls, ownership, and delivery options that teams can reason about.
03 / Platform Design
Create the paved road
Turn repeated decisions into standards, SDKs, templates, secure defaults, and platform capabilities that reduce cognitive load.
04 / Implementation
Keep architecture executable
Build close to the code, validate assumptions early, and make design choices visible through working delivery paths.
05 / Software Lifecycle
Design for operation
Carry decisions into CI/CD, observability, readiness, security controls, cost, support, and service ownership.
06 / Feedback Loop
Evolve the standard
Use delivery evidence, incidents, friction, and team feedback to improve the platform and strengthen enterprise capability.
DEL / 05Projects
Projects
Delivery experience across migration, platform, identity, and global operations.
I am a Principal Engineer who started in first-line support and developed through service desk, engineering projects, CloudOps, and infrastructure. Combined with a degree in International Relations and Politics, that gives me a strategic eye and a practical understanding of how technology lands with teams, services, and organisations.
On-premises to Azure Cloud migrations
Shaped migration strategy and implementation paths for moving legacy capability into Azure, balancing service continuity, security controls, platform readiness, and operational ownership.
Proof-of-concept internal developer platform
Produced a POC IDP focused on delivering value quickly: proving self-service workflows, reusable templates, and paved-road deployment patterns before committing to full platform scale.
Fully fledged internal developer platform
Created an IDP model designed for horizontal capability scaling, giving teams repeatable foundations for building, deploying, operating, and governing services without central bottlenecks.
Tooling deployed to Kubernetes
Deployed and supported engineering platforms on Kubernetes, including CloudBees and monitoring stacks built around Prometheus, Grafana, and related operational tooling.
Standardised service foundations
Architected capability for identity management, SSO, and application enablement through templated Python projects with Docker support, CI/CD, and Kubernetes manifests built in.
Application support across regions
Built experience supporting global applications, working with chase-the-sun teams, international stakeholders, and globalised entry systems where reliability and communication mattered as much as code.
OPS / 06Tooling
Tooling
Experienced across the stack that turns architecture into delivery.
Platform and runtime
- Docker
- Podman
- Kubernetes
- Linux first
Distributed systems and workflow
- Temporal
- Dapr
- Service orchestration
- Workflow design
- Integration patterns
Delivery and governance
- GitOps
- Argo CD
- Flux
- Atlassian
- CloudBees
- Azure DevOps
- Black Duck
Cloud, storage, and infrastructure
- Azure
- AWS
- DigitalOcean
- HashiCorp
- MinIO
- Ceph
Architecture and modelling
- TOGAF
- ArchiMate
- UML
- Archi
- Enterprise architecture
- Solution design
Languages
- C#
- Python
- JavaScript
- Go
- SQL
Data systems
- MySQL
- Postgres
- MSSQL
- Cassandra
- MongoDB
- Cosmos DB
Automation and scripting
- Terraform
- Ansible
- Bash
- PowerShell
- Zsh
EA / 07Enterprise Architecture
Enterprise Architecture
My direction is toward architecture that shapes enterprise capability.
I want to move further into enterprise architecture because the work I value most sits above any single service, platform, or implementation choice: clarifying capability, ownership, governance, and the operating model that lets engineering scale with intent.
Move from shaping individual platforms and delivery paths into defining the enterprise capabilities they support.
Connect business intent, governance, operating models, and technical strategy so architecture decisions stay executable.
Use deep platform engineering experience to make enterprise architecture practical, testable, and grounded in delivery evidence.
Capability
Map business outcomes, value streams, services, platforms, data, and ownership so technical decisions connect to enterprise intent.
Governance
Create standards, guardrails, decision records, risk controls, and architecture principles that help delivery rather than slow it down.
Ownership
Clarify who owns the capability, who operates it, how teams consume it, and where autonomy needs a clear control surface.
Evidence
Use delivery data, incidents, cost, security posture, and developer friction to evolve standards from observed reality.
REF / 08Influences
Inspirations
People who shape how I think about systems, platforms, and strategy.
Eric S. Raymond
His writing on open source culture connects to the way platforms grow through participation, feedback, and useful defaults.
Gregor Hohpe
His work on architecture, integration, and platform thinking reflects the kind of practical enterprise architecture I value.
John Carmack
A model for deep technical clarity, performance awareness, and the habit of reducing hard problems to executable reality.
Steve Wozniak
Represents elegant technical design that makes powerful capability accessible, useful, and enjoyable for real people.
Linus Torvalds
Linux shows how strong technical stewardship and modular architecture can create durable capability at global scale.
Dennis Ritchie
C and Unix shaped the engineering foundations behind modern systems: simple abstractions, composability, and operational control.
Stuart Russell
His work helps frame AI as a system of goals, constraints, uncertainty, and alignment rather than just tooling.
Peter Norvig
Bridges computer science, AI, and pragmatic engineering in a way that values clarity, evidence, and useful implementation.
Plato
Useful for thinking about ideals, governance, knowledge, and the gap between abstract models and lived institutions.
Thomas Hobbes
Relevant to architecture as a control problem: authority, incentives, risk, and why systems need explicit operating rules.
Hans Morgenthau
A reminder that organisations are shaped by interests, power, trade-offs, and constraints, not just rational design.
Kenneth Waltz
His structural view of international systems maps neatly to enterprise thinking: behaviour is shaped by the system around it.
Ian Anderson shaped the attitude behind this site.
Ian Anderson’s work at The Designers Republic turns systems, grids, noise, compression, and industrial graphics into something precise but alive. I chose that influence for this site because it matches the way I think about platform engineering: structured, opinionated, technical, slightly confrontational, and built around clarity under pressure rather than soft decoration.
AI / 09New Age
AI and the New Age
AI, architecture, and platforms are becoming one strategic conversation.
I believe AI will change the horizon for enterprise architecture and platform engineering. The opportunity is enormous, but so are the new questions around trust, operating models, data boundaries, capability ownership, governance, and how organisations avoid turning experimentation into unmanaged risk.
AI changes the shape of architecture
AI is not just another tool in the stack. It changes how organisations think about knowledge work, automation, decision support, governance, integration, and the platforms needed to make those capabilities safe and repeatable.
Platforms become the control surface
The next horizon is not isolated AI experiments, but governed platforms that let teams use AI with identity, policy, observability, data boundaries, cost controls, and delivery workflows built in from the start.
Powerful does not mean conscious
Reading Russell, Norvig, and Goodfellow reinforces that modern AI remains mathematical modelling at scale. It can reason impressively in form, but it can also behave like a stochastic parrot. Organisations need ambition, but also humility.
I am also interested in what comes after today’s dominant von Neumann-style input/output model: neuromorphic computing, Turing-esque questions about machine behaviour, and whether something closer to a living intelligence is possible rather than a system that only simulates thought through prediction.
COM / 10Contact
Contact
Let’s talk platform engineering and architecture.
I’m interested in secure delivery, reusable engineering systems, practical architecture, and platform teams that create durable leverage.