I am a DevOps and Site Reliability Engineer, and a self taught programmer. I spend my days making production systems easier to run, easier to understand and less likely to wake anyone up at 3AM.

What I focus on

My current area of focus is Site Reliability Engineering, which includes observability, stability, infrastructure improvements, automation, figuring out performance bottlenecks, troubleshooting systems on fire and preaching SRE practices.

Increasingly that overlaps with security. The same properties that make a system reliable — a small attack surface, credentials that are scoped and rotated, changes you can audit, failures you can actually see — are the ones that make it defensible. Reliability work that ignores an adversary is only half done.

What I can help with

  • Reliability — SLOs that describe something a user would actually notice, alerting that does not cry wolf, incident response and blameless postmortems
  • Observability — Metrics, logs and traces you can genuinely debug from, instead of dashboards nobody opens
  • Delivery — CI/CD pipelines that are boring on purpose, so releases stop being events
  • Security — Threat modelling, secrets handling and key management, hardening build and deploy pipelines
  • Cloud and infrastructure — AWS and Terraform, containers and Kubernetes, and an honest opinion on when not to reach for them
  • Performance and troubleshooting — finding the actual bottleneck, whether it lives in the JVM, the database or the architecture itself

Things I work with

Linux, AWS, Terraform, Kubernetes and Helm, Prometheus and Grafana, GitHub Actions and the usual DevSecOps suspects.

Get in touch

Always happy to talk shop, whether it is a reliability problem you are stuck on, bounce ideas or something you think I have got completely wrong.

You can also find me on the Internet:

[email protected]
LinkedIn
GitHub
Stack Overflow