I do cloud infrastructures — I make them work, work right, work well, work cheap — in that order!
This section is a kind of a professional one-pager (for a 6-pager, see my CV) and perhaps a little about what drives me as an engineer.
I’ve held various roles in my career – in web-development, ICT, QA, systems engineering, cloud. I started out in web development in the early 00’s but turned to systems after becoming interested in other forces that make infrastructure work — networking, virtualization & elastic capacity, self-service models, service oriented architectures, distributed & self-healing systems, consistency vs availability tradeoffs, etc were all enablers but the combined utility of these 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. ٩(⁎❛ᴗ❛⁎)۶