# Building Reusable Infrastructure with Terraform Modules ## Or: How I Finally Stopped Copy-Pasting the Same 200 Lines of Code

Day 8 of the 30-Day Terraform Challenge — and today I learned the secret that separates people who "know Terraform" from people who actually build infrastructure at scale. Modules. You know that feeling when you've written the same security group configuration three times? Or when you're about to copy-paste your entire web server cluster for the fifth environment? That's the feeling modules were made to eliminate. The Problem: Copy-Paste Engineering Let me show you what I was doing before today: # dev/main.tf resource "aws_lb" "web" { name = "dev-web-alb" # ... 200 more lines ... } # staging/main.tf resource "aws_lb" "web" { name = "staging-web-alb" # ... THE SAME 200 lines, different name ... } # production/main.tf resource "aws_lb" "web" { name = "prod-web-alb" # ... 200 lines, again ... } This is what we call Copy-Paste Engineering . It's fast. It works. And it's a nightmare to maintain. Change the health check path? That's 3 files. Fix a security group rule? 3 files. Update the AMI