Infrastructure-as-code is not a new topic for the Full Stack Journey podcast—we’ve discussed it in episode 27 (understanding Terraform and using “defensive Terraform”), episode 30 (focused on Pulumi and using general-purpose programming languages for infrastructure-as-code), episode 32 (talking about Lyra), and episode 35 (testing and validation for infrastructure-as-code). Surely this topic has been fully explored, right? Nope! In today’s show, Scott is joined by Tim Davis (@vtimd on Twitter), Developer Advocate at Env0, to talk about the challenges of scaling infrastructure-as-code beyond a single engineer. Scott and Tim provide practical insights into these challenges and ways to address them. Some of the topics we cover include: * Issues with scaling infrastructure-as-code * Managing state–do you need more than just a central storage location? * How to handle variable values * What is TACOS? * The drift problem–what it is, and how to address it If you’re new to infrastructure-as-code, or if you’re seeking advice on how to scale it to your entire team, this conversation is sure to provide useful information. Show Notes: @vtimd  – Tim Davis on Twitter Env0 The DevOps subreddit Terraform Cloud Scalr