Brooklyn, New York, United States
I've been doing infrastructure work with Unix/Linux systems forever. I've been gravitating more and more over the years towards programming, and I'd like to make that my primary focus, but infra can still be in there too. I'm particularly big on Go and Python, and I've worked with Kubernetes, VMs, containers, monitoring, CI/CD, GitOps, Infrastructure as Code... you get the idea. Here are some excerpts from a document I wrote about working with me: Level of Concern: Engineering Philosophy As an engineer, I’m basically a professional pessimist. (The phrase “cheerful negativity” says a lot about my personality.) I see my job as thinking of everything that can possibly go wrong, and preventing or mitigating it. That covers a lot of ground: not just errors and latency, but also human factors. I document everything, make checklists, and point out possible pitfalls, then make it as hard as I can to fall into them. I take into account that people have different levels of knowledge, experience, and memory - including the same person calmly coding on an afternoon vs. trying to fix that code 6 months later at 3 AM when everything is on fire. It Just Works: Automation Given my penchant for details and my professional pessimism, it shouldn’t be surprising that I like automation. I generally gravitate towards making things as robust as possible, and part of that is eliminating possibilities for human error, as well as toil. I find satisfaction in making things Just Work, and I have tended to work on tools and platforms, with the goal of making them seamlessly do tasks while still being super flexible.