Why clicking in consoles stops working
Your first cloud resources come from clicking. You open the AWS console, click through a wizard, create a server. It works, and clicking feels productive. Then reality arrives: you need an identical staging environment and can't remember the 14 settings you picked. A teammate asks how the network is configured and the only honest answer is "let me click around and check." Something breaks and nobody knows what changed, because clicks leave no record. Clicking doesn't scale, doesn't repeat, and doesn't remember.
The fix is to describe your infrastructure in text files, commit them to Git, and let a tool build exactly what the files say. That's Infrastructure as Code (IaC), and Terraform is the most widely used tool for it. This article gets you from zero to understanding the whole core loop, and writing real Terraform you can run.
Note: Who this is for: Anyone who's created cloud resources by clicking and sensed there must be a better way. No Terraform experience needed. Knowing roughly what a cloud server or network is helps, but we explain as we go. Examples use AWS; Terraform works with every major provider.
What Infrastructure as Code actually is
