The majority, and probably close to 80%, of the Terraform code I see is not idiomatic. It doesn't follow the design principles the language creators set forth. I will talk about module structure in this article. This is one example of Terraform (anti-) patterns that has direct impact on operations.

There's quite a bit of value to knowing who your customer is. For one, you'll better understand what's important for the business, and you'll be able to avoid deep pits that could get you (or your customer) into trouble. In my opinion, this kind of research makes sense, even if you're a software engineer. We're not trying to match some regulatory requirement, which means we can keep this light.

This crib sheet is directed at people who manage some kind of infra footprint. The idea originated from a conversation about how someone would expect a "senior engineer" to map out some kind of forward-pointing plan for the aforementioned infra footprint.