Work that can be examined.

Customer confidentiality matters, so this page separates reported outcomes from public technical artifacts. No borrowed logos, inflated case studies or private architecture details.

01Reported customer outcome

Production Kubernetes troubleshooting

Across 20 public customer reviews, every rating is five-star. Feedback repeatedly points to fast problem comprehension, clear communication, strong Kubernetes and AKS diagnosis, responsiveness and willingness to work together again.

~2 hours

In one reported engagement, an issue that had occupied the customer for three days was diagnosed and resolved in about two hours.

Aggregated and anonymized. This is reported customer feedback, not a customer-approved case study.

02Public talk / 2024

Repeatable Azure infrastructure

A practical Azure Conf session on Terraform, repeatable cloud provisioning and making infrastructure changes auditable.

TerraformAzureInfrastructure as code

03Engineering education

A 48-hour DevOps learning path

A hands-on programme connecting Linux, Python, Git, CI/CD, Docker, Terraform, cloud and Kubernetes as one operating system rather than isolated tools.

TeachingDeveloper experienceSystems thinking

04Open source

Infrastructure tools in public

Projects including GEPP and CIMME turn recurring operational work into reusable software. The repositories expose the implementation choices, documentation and maintenance history for inspection.

Explore open-source work ↗

05Long-form practice

182 dated technical records

The archive begins in 2011 and traces a practical path through Python and Linux, electronics and IoT, containers, distributed infrastructure and cloud-native operations.

Browse the archive ↗

20 / 20

five-star public customer ratings

technical books

182

dated technical records

13+

years of public technical work

Start with the real problem

A strong engagement starts with inspectable evidence.

Send the problem, current baseline and what the team needs to decide. The proposed scope will state outputs, exclusions and the evidence used to judge the result.

Discuss your system