Pinned post
Reminder that I'm looking for a new role.
I'm an experienced infrastructure engineer. I've worked with Kubernetes, Terraform, Postgres, AWS, with some Azure and GCP as well.
I've also done a lot of valuable work as a backend engineer, having worked primarily in Haskell and Rust, though I've also gotten my hands dirty with Python, some Go, C++, and a bit of TypeScript.
I've also had the privilege of being a public speaker, and have also lead training seminars for peers on how to use different tools, sharp edges to avoid, and getting them to a functional mental model of how things work quickly, so they can start to ask meaningful questions and debug problems on their own.
I take ownership quickly, care deeply about reliability, correctness, and delivering quality service to customers. I say this up-front because this comes with a number of downsides, including:
* I dislike shoddy work, buggy code, leaky abstractions, or flaky services. "Don't let the perfect be the enemy of the good" is fine and well, but tech debt brings an aggressive drag coefficient to your business, and that fact gets swept under the rug far too often.
* I don't optimize for shipping a ton of code quickly. I tend to be on the lower end of lines of code/sprint, and I'm not terribly keen on changing that. I write code to be maintainable, have clear invariants, be easy to refactor as business needs change, be easy to debug, and to quietly work while you're focus is elsewhere.
I'm also a quick study, and have a long history of getting spun up quickly on the new parts of a stack I encounter at the various roles I've filled over the years.
If this sounds like a good fit, please do drop me a line. I'd love to talk about how I can make your life better.
thewizardtower.github.io/McCulloughAdam…
I'm an experienced infrastructure engineer. I've worked with Kubernetes, Terraform, Postgres, AWS, with some Azure and GCP as well.
I've also done a lot of valuable work as a backend engineer, having worked primarily in Haskell and Rust, though I've also gotten my hands dirty with Python, some Go, C++, and a bit of TypeScript.
I've also had the privilege of being a public speaker, and have also lead training seminars for peers on how to use different tools, sharp edges to avoid, and getting them to a functional mental model of how things work quickly, so they can start to ask meaningful questions and debug problems on their own.
I take ownership quickly, care deeply about reliability, correctness, and delivering quality service to customers. I say this up-front because this comes with a number of downsides, including:
* I dislike shoddy work, buggy code, leaky abstractions, or flaky services. "Don't let the perfect be the enemy of the good" is fine and well, but tech debt brings an aggressive drag coefficient to your business, and that fact gets swept under the rug far too often.
* I don't optimize for shipping a ton of code quickly. I tend to be on the lower end of lines of code/sprint, and I'm not terribly keen on changing that. I write code to be maintainable, have clear invariants, be easy to refactor as business needs change, be easy to debug, and to quietly work while you're focus is elsewhere.
I'm also a quick study, and have a long history of getting spun up quickly on the new parts of a stack I encounter at the various roles I've filled over the years.
If this sounds like a good fit, please do drop me a line. I'd love to talk about how I can make your life better.
thewizardtower.github.io/McCulloughAdam…
