I do cloud infrastructures — making them work, work right, work well, work cheap — in that order!
This page here is a bit of a professional one-pager (for a 6-pager, see my CV .. and no I don’t work for Amazon).
Perhaps a little about what drives me as an engineer.
I’ve worked in various technology settings over 17 years – in content & web development, SOHO infrastrcture & networking, QA automation, systems admin & engineering, DevOps/SRE, cloud infra.
After university the first time, I tried my hand at programming but the appeal of web development didn’t take my fancy. I was more interested in the backends and the things behind the scenes that make things work — networking, virtualization & elastic capacity, self-service models, service oriented architectures, distributed & antifragile systems, etc. These didn’t have the modern labels we assign them today but being business enablers, their combined utility eluded all but the biggest companies in the pre-cloud era. Seeing cloud providers now package-up and commoditise these to the extent that players in every field are by default cloud-native is testament to a universal need for dependable infrastructure not just as a consumable but a platform. Yet cloud platforms offer more than just a means to offload complexity to the provider, their adoption shapes a necessary antifragility for consumers — engineering systems with this agency at the core, for continuous improvement, is my main professional interest.
When I am not busy in production I like engineer away “pothole problems” with code and contribute my part to better infrastructure state of play (I’d ❤️ if more of my work was open source). I am still a developer of sorts given my early career prologue with code and perhaps this defines what SREs are — tamers of systems using (mostly) software engineering principles. I am a keen proponent of Software-defined-everything and evangelize Infrastructure-as-Code to be the authority that controls all aspects of infrastructure.
Where required, I also play a part in the “hands-off” albeit instrumental work in this domain — systems analysis, solution & process design, architecture, agile delivery, tech culture, etc (some of these seem contra-agile but ask me why agile delivery in infra requires following a plan over responding to change).
Agile, software engineering, economics, experiental learning & continuous improvment — these are my elements in the endeavour of dependable and flexible infrastructures. ٩(⁎❛ᴗ❛⁎)۶