I'm a technologist, operations engineer, product developer, and solver-of-problems-with-duct-tape. My previous career in high-assurance architecture has driven me to develop an operations mindset for robust and observable technology. I have a proven nose for hunting down and eliminating technical debt and process inefficiencies in organizations of all shapes and sizes. This is my blog.
I started my working life as an architect — buildings, not software. I designed and oversaw construction of life safety critical infrastructure: power systems and post-9/11 site hardening for the telecom industry, biosafety laboratories for deadly disease research, and clean room manufacturing and hazardous materials handling facilities for the pharmaceutical industry. But in an industry which like many others is being eaten by software, I quickly fell into a technical role as an expert in developing tools for estimation and CAD automation, as well as information-rich 3D modeling (also known as Building Information Modeling or BIM). I've turned my skills in designing secure and safe architectural environments into an inspiration to focus on building rock-solid information systems.
Currently I'm a product manager at Joyent where my work is focused on application blueprints for the Autopilot Pattern and leading the development of ContainerPilot. I develop, write about, and talk about projects that demonstrate the best practices for container-native deployments on Joyent's Triton platform. Triton is a Docker API wrapping Joyent's existing bare-metal containerization technology built on Solaris zones, and it's pretty awesome so you should give it a try.
Before I joined Joyent, I managed the operations team and the software infrastructure for DramaFever. We ran a large scale microservices architecture on AWS for millions of users. I built our scrappy team of operations engineers from scratch (as well as our IT team). My team had responsibility over builds and deployments, site reliability engineering, performance monitoring and improvements, and developing our video transcoding and analytics ingest pipelines. The work I led at DramaFever was featured as a case study in the O'Reilly book Effective DevOps, by Jennifer Davis and Katherine Daniels.
When it comes to writing software, I work mostly with Python and Go and have professional experience with C# and AutoLisp. I have some training in security design and pen-testing, and like to crack open some shell code now-and-then to keep my skills sharp. I've dabbled in C, Erlang, Node.js, and Rust, and have a strong interest in learning more about language internals and low-level systems programming.
The code of this blog and all code content is MIT licensed, except where a given piece of code is attributed to another author and has a different license. The original written prose and images in this repo are licensed under Creative Common Attribution 3.0 Unported License. All opinions expressed are solely my own and not those of my employer. This blog is in no way endorsed by any third-party.
Public conversations in Twitter or Github are great, but feel free to send me an email if you need to reach me privately.
If you are sending me anything of a confidential nature, please use PGP encryption. Sending my personal data in the clear is a good way to avoid having to do business with me in the future. PGP public key: 6F725947