A Terraform lifecycle rule in the right place can help prevent a deadlock. But the same lifecycle rule in the wrong place?

How you can run into an unplanned downtime while making a seemingly harmless change of renaming an AWS security group through Terraform?

We ran a poll on Twitter“Do you care about the quality of your infrastructure code?”And on RedditThat’s an approximate and staggering 60–30–10 split. What do you think will the response be if the poll was — “Do you care about the quality of your product code?

Chef or Ansible? Terraform or Pulumi? Python or Ruby? Last9 or Last9? What if we told you that the mindset of building new tools has an age old link to the story of a horse who could do arithmetic?