--- title: Day 25/30: “I clicked around until it worked” is not... description: A short daily post argues for Infrastructure as Code as a way to make cloud environments reproducible and reviewable, contrasting it with undocumented,... canonical: https://daily.dev/posts/day-25-30-i-clicked-around-until-it-worked-is-not-documentation-qejzgnyh7 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Day 25/30: “I clicked around until it worked” is not documentation | daily.dev og:description: A short daily post argues for Infrastructure as Code as a way to make cloud environments reproducible and reviewable, contrasting it with undocumented,... og:url: https://daily.dev/posts/day-25-30-i-clicked-around-until-it-worked-is-not-documentation-qejzgnyh7 og:image: https://api.daily.dev/og/posts/qeJzGnYH7.png og:image:alt: Day 25/30: “I clicked around until it worked” is not documentation og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Day 25/30: “I clicked around until it worked” is not documentation **[Ezile Mdodana](https://daily.dev/sources/7vb9selrkhohgnzepmfvq)** · [@ezilemdodana](https://daily.dev/ezilemdodana) · 1 min read · 3 upvotes · 1 comments ## Summary A short daily post argues for Infrastructure as Code as a way to make cloud environments reproducible and reviewable, contrasting it with undocumented, manually configured servers. It highlights AWS CloudFormation and AWS CDK as tools that let development, testing, and production environments follow the same blueprint, reducing reliance on tribal knowledge. ## Content Infrastructure as Code lets you define cloud resources using code. Tools such as AWS CloudFormation and the AWS CDK can create repeatable, reviewable environments. This means development, testing and production can follow the same blueprint. It also reduces the mystery of the one server that only works because someone changed a setting three years ago. If infrastructure matters, it should be reproducible, not dependent on Trevor remembering what he clicked. #AWSWithoutTheFluff #InfrastructureAsCode #AWSCDK ## Community discussion Top comments from developers on daily.dev. **@vergissberlin** · 0 upvotes > The part IaC alone doesn't solve is what happens during an incident, when someone opens the console and changes a setting under pressure to fix something right now. Without drift detection running regularly, that change quietly diverges from the template and you're right back to "it works because of what Trevor clicked" - just with an extra layer of code nobody trusts anymore because it no longer matches reality. ## Similar posts on daily.dev - [Some Data Should Be Code](https://daily.dev/posts/some-data-should-be-code-tjcjklg9y) · Lobsters · 1 upvotes · 0 comments - [Infrastructure as Code with APIs: How to Automate Cloud Resources the Developer Way](https://daily.dev/posts/infrastructure-as-code-with-apis-how-to-automate-cloud-resources-the-developer-way-6bbfaerso) · freeCodeCamp · 2 upvotes · 0 comments - [IaC Testing for DevOps: Types, Tools & Examples](https://daily.dev/posts/iac-testing-for-devops-types-tools-examples-wt3io8o20) · Spacelift · 1 upvotes · 0 comments - [From clickops to governed IaC: CloudFormation drift detection in practice](https://daily.dev/posts/from-clickops-to-governed-iac-cloudformation-drift-detection-in-practice-velwpwbmh) · AWS · 1 upvotes · 1 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#iac](https://daily.dev/tags/iac), [#aws-cloudformation](https://daily.dev/tags/aws-cloudformation) [View this post on daily.dev](https://daily.dev/posts/day-25-30-i-clicked-around-until-it-worked-is-not-documentation-qejzgnyh7) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/day-25-30-i-clicked-around-until-it-worked-is-not-documentation-qejzgnyh7","headline":"Day 25/30: “I clicked around until it worked” is not documentation","text":"A short daily post argues for Infrastructure as Code as a way to make cloud environments reproducible and reviewable, contrasting it with undocumented, manually configured servers. It highlights AWS CloudFormation and AWS CDK as tools that let development, testing, and production environments follow the same blueprint, reducing reliance on tribal knowledge.","url":"https://daily.dev/posts/day-25-30-i-clicked-around-until-it-worked-is-not-documentation-qejzgnyh7","datePublished":"2026-08-24T07:11:05.941Z","dateModified":"2026-09-13T21:21:42.751Z","author":{"@type":"Person","name":"Ezile Mdodana","url":"https://daily.dev/ezilemdodana","image":"https://media.daily.dev/image/upload/s--1OI8gwnO--/f_auto/v1771923757/avatars/avatar_7vB9SeLRKhOHGnzEpmFvQ?_a=BAMAMiiu0","description":"Software Project Lead sharing practical insights on NestJS, Angular, AWS and scalable systems.","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":8430}},"image":"https://media.daily.dev/image/upload/s--qun-WDqO--/f_auto/v1787555467/posts/qeJzGnYH7?_a=BAMAMicg0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"comment":[{"@type":"Comment","text":"The part IaC alone doesn’t solve is what happens during an incident, when someone opens the console and changes a setting under pressure to fix something right now. Without drift detection running regularly, that change quietly diverges from the template and you’re right back to “it works because of what Trevor clicked” - just with an extra layer of code nobody trusts anymore because it no longer matches reality.","datePublished":"2026-09-01T21:57:02.115Z","url":"https://daily.dev/posts/qeJzGnYH7#c-xSXcOVUzp","author":{"@type":"Person","name":"André Lademann","url":"https://daily.dev/vergissberlin","image":"https://avatars.githubusercontent.com/u/179964?v=4"}}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/sources/7vb9selrkhohgnzepmfvq","name":"Ezile Mdodana"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Ezile Mdodana","item":"https://daily.dev/sources/7vb9selrkhohgnzepmfvq"},{"@type":"ListItem","position":3,"name":"Day 25/30: “I clicked around until it worked” is not documentation"}]} ```