Point solution infrastructure as code (IaC) templates get very tiresome very fast, because they're not reusable.

In a previous post, I discussed the topic of vendor lock-in with cloud providers, and why I thought it was over-emphasized. I'd like to further highlight my stance using a real-life example of actual vendor lock-in, which, in my opinion, is more concerning.

In the last few systems and services I've designed for cloud, I've taken an approach of starting with the limits and working backwards.

People have been wondering about how I created my themed terminal setups, so I thought I'd make a post about it.

I wanted to capture some thoughts on deployment approaches for OpenAI in a large enterprise.

We are better as people and as organizations when we connect with each other.

This week I am at a conference I've admired from afar but have not yet had the chance to go to, until now: the PowerShell + DevOps Global Summit.

The year was 2013. I was less than one year into my first job, and Google had just released Google Glass.

As engineers, we're always in search for the One True Way to accomplish a task, when more often I believe we should be focusing on supported options.

There are some things that I search in real search engines that have real answers out there, but the top 10 results from Google and Bing are all marketing silliness.