I built a tool called LaunchStack that turns a short wizard into a full production-ready Azure stack — Terraform modules, Helm charts, CI/CD pipelines, monitoring dashboards, the works. No more starting every project's infra from a blank repo.
Before writing more code, I wanted to know one thing: does this actually hold up when someone outside my own head tries it? So I posted it on r/Terraform, expecting either silence or a handful of polite "cool idea" comments.
I got neither. I got told exactly what was wrong with it — and that turned out to be more valuable than a hundred passive upvotes.
What happened
The post did well by Reddit's standards — #4 on r/Terraform that day, 1.5K+ views within a couple hours, real comments. But the upvote ratio told a different story than the view count: people were engaging, and a chunk of them weren't happy.
Two comments in particular changed how I think about the product:
"Where are the sources?"
Fair. I was asking strangers to trust a wizard's output without showing them what that output actually looked like first. Nobody serious signs up for an unknown tool just to maybe see something useful at the end.
"Nah bro, I'm not giving you my email to test this... there's no examples or nothing."
This one stung a little, but it was the more important comment of the two. My dev environment required a real login (Microsoft/Google OAuth) before you could see anything the wizard produced. To me, that was just... how OAuth works. To a skeptical reader scrolling past a new account's link, it looked exactly like a lead-capture trap.
Both comments were versions of the same underlying problem: I was asking for trust before I'd earned it.
What I changed
Two fixes, both shipped within the hour, directly in the comment thread:
- Added a placeholder-email option for the dev environment, so trying the wizard didn't require handing over anything real.
- Published a sample generated repo on GitHub — folder structure, actual rendered Terraform/Helm output, screenshots — so anyone could see exactly what the wizard produces without running it at all.
That second one mattered more than I expected. It turned "trust me" into "here, look for yourself" — which is a much easier ask.
The technical feedback itself
Buried under the trust-and-friction comments was the actual thing I was there for: real questions about the generated output — someone asking about multi-cloud support (AWS/GCP), others poking at the architecture choices in the AKS stack. That's the conversation I was hoping to have from the start, and it only really opened up once the friction was addressed.
The unglamorous part: fighting AutoMod
Worth mentioning since it's not talked about much: a brand-new Reddit account posting links gets aggressively filtered. One of my own comments got auto-hidden for low karma. Later, editing the post to add the sample-repo link sent the entire post back into a manual review queue — even though it had already been live and performing for hours.
The fix was boring but effective: a short, honest message to the subreddit's mods explaining what happened. They reinstated everything within a couple hours. No drama, just a queue.
If you're planning to post something similar from a fresh account, budget for this. It's not a sign your content's bad — it's just how spam filtering works at scale, and low-karma accounts get caught in the net along with actual spam.
What I'd tell someone about to do this
- Ask for criticism explicitly, and mean it. "Tear it apart" as a literal instruction changes what people feel comfortable saying.
- Remove every unnecessary barrier before you post, not after. I found out about the login-wall problem the hard way; I could've just... not required real login for a dev demo in the first place.
- Show the output before asking for the interaction. A sample repo or screenshots up front would have prevented half the pushback entirely.
- Reply fast, and don't get defensive. Every reply I gave that started with "fair feedback" did more for the thread's tone than any amount of explaining myself would have.
LaunchStack is still in dev, Azure-only for now (AWS/GCP planned once this is solid). If you want to see what the wizard actually outputs before trying it yourself, the sample repo's linked below.
Sample output repo: github.com/muthusethu/launchstack
Top comments (0)