Vibe Coding Your Infrastructure
The article discusses the challenges of using AI to manage infrastructure code, specifically with Terraform. It highlights the difficulty of making informed decisions about infrastructure settings without sufficient context from application code. The author argues that separating application and infrastructure code leads to mistakes that are hard to catch during code reviews.
- ▪AI can generate HCL code for infrastructure, but it struggles with decision-making due to lack of context.
- ▪Infrastructure decisions like IAM scopes and timeouts are critical and often made blindly by AI.
- ▪The separation of application and infrastructure code complicates reviews and increases the risk of production outages.
2 outlets in our directory ran this story, first to last over 1 hour. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Vibe coding without true knowledge — r/webdev
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ivan |
| Canonical URL | https://www.ivan.codes/blog/vibe-coding-infrastructure |
| Publication time | Mon, 25 May 2026 17:53:10 +0000 |
| Retrieval time | 2026-05-25T18:07:39.397Z |
| Last seen | 2026-05-25T18:07:39.397Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | _Enbwdg8ezvE · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
On vibe coding your infrastructureWhat happens when you point AI at your Terraform, and why infra-from-code frameworks are the structural fix.After I wrote about letting the AI cook on application code, a few people came back with the same pushback. Sure, that works for the route handlers and the database queries, but what about the infrastructure? Are you handing Terraform to the model and just letting it run? I'm not, and that's the place where the whole approach breaks down for me. The model writes HCL fine, that part has never been the issue. The hard part of infrastructure work is the decisions that go into each line, like sizing and retention and IAM scopes and timeouts, and the application code gives the model almost nothing to work with on any of them.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ivan.
Discussion
0 commentsMore from Ivan
