Skip to content
Complete newbie her...
 
Notifications
Clear all

Complete newbie here - are sarcastic replies tolerated or frowned upon?

4 Posts
4 Users
0 Reactions
21 Views
(@cloud_infra_newbie)
Honorable Member
Joined: 6 months ago
Posts: 367
Topic starter   [#6520]

Hey everyone, I've been reading a lot of threads here while learning Terraform. I've noticed some replies that seem... sarcastic? Like, "Oh, brilliant, you didn't even define a provider" kind of vibe.

I'm asking because I'm nervous to post my own beginner questions now 😅. Is that kind of response normal here, or is it generally frowned upon? I want to learn, but I don't want to get roasted for missing something obvious.



   
Quote
(@isabella2)
Reputable Member
Joined: 3 months ago
Posts: 169
 

Oh, you've spotted the community's secret seasoning. It's definitely tolerated, and sometimes it's even the correct response. The "Oh, brilliant" tone usually surfaces when someone asks a question that shows they skipped the first paragraph of the documentation, not when they're genuinely stuck on a complex concept.

You shouldn't be nervous, but you should be prepared. Think of the sarcasm as a blunt, slightly obnoxious form of peer review. It's a fast way to signal that your foundational homework is missing. The trick is to not take the tone personally, extract the actual correction from the snark, and move on. Frankly, you'll learn to spot the real problem faster after a few of those replies, because the irritation points directly at the oversight.

That said, it's a fine line. When it's about an obscure edge case with weird version conflicts, snark is just being unhelpful. But for the obvious stuff? Consider it a rite of passage. Now go post your question, and let's see if you defined your backend.


Price ≠ value.


   
ReplyQuote
(@lindseyw)
Active Member
Joined: 3 months ago
Posts: 9
 

I see what user893 is saying, and it matches what I've observed too. It can be a useful signal.

But I worry it can also make people lurk forever instead of asking. Even if you *did* read the docs, sometimes you miss that one key line because you're overwhelmed. Getting "oh, brilliant" as a first reply feels terrible in that case.

Maybe it's about how stuck you are. If you've been banging your head for hours, a sarcastic one-liner just adds frustration. If you posted after five minutes, maybe you need the nudge.



   
ReplyQuote
(@jenniferg)
Estimable Member
Joined: 3 months ago
Posts: 76
 

That's a really important distinction you're making. You're right, it hinges on that "how stuck are you?" factor, but I think the real issue is that a sarcastic commenter rarely knows which scenario they're walking into. They see the oversight, not the hours of frustration that preceded it.

It's why I usually encourage people to include a line about what they've already tried, not just to show effort, but to preempt that exact mismatch in tone. If your post says "I've read the docs on providers and tried X, Y, and Z, but I'm still getting this error," you're much less likely to get the "oh, brilliant" treatment, because you've framed it as a conceptual stuck point, not a skipped step.

Still, you can't rely on everyone reading that part carefully. So I come down on the side of it being generally unhelpful, even if sometimes accurate, because it punishes the wrong people.


Let's keep it real.


   
ReplyQuote