Redimates Add to Chrome — Free

Community guides · Programming

Before you reply in r/coding — the rules nobody writes down

637K subscribers·17 years old·Top post this month: 376↑·Top comment: 80↑

Drop a comment in r/coding and you're talking to senior engineers who've shipped the thing you're recommending. Generic advice doesn't land; specific gotchas do.

What's hot in r/coding now

What people are actually discussing

Top threads from the last month — what's getting engagement right now.

What this sub rewards

How replies earn upvotes here

  • Senior-level technical depth is expected; avoid generic advice. Drop the 'try this' language. Show the code, the gotcha, and the production consideration.
  • Concrete code or runnable examples are welcome where relevant. Snippets beat prose. Three lines with one comment beats a paragraph of explanation.
  • Acknowledge limitations, trade-offs, or uncertainty when relevant. Name when your approach breaks — concurrency, scale, legacy version, OS-specific.

What good looks like

Real comments that landed in r/coding

Two recent highly-upvoted replies. Notice what they have in common — concrete, no preamble, no self-promotion.

"I agree completely with all of this. My company (a huge telecommunications company) is moving to bo-touch-code and ai-dlc. As a tech lead, we are encouraged to use ai for everything (kiro) - breaking down architecture into tickets, coding, bugs, code reviews, et al. It is pretty impressive, tbh. I have always been a huge proponent of automating the boring…"

u/ma929tt, 69 ↑ on "Agentic Coding is a Trap | Remaining vigilant about cognitive debt and atrophy"

"When I worked at big tech it was more that basically no body gave a shit so it was a culture of shit quality. The only thing that mattered was closing out the jira ticket and the acceptance criteria was basically as shallow as, the thing exists. If you want well structured good code it has to be a wide…"

The one rule that gets posts removed

Broad programming topics — focus on transferable concepts.

Your pre-reply checklist

Before you hit Reply — four quick checks

Does my comment add something specific, not just an opinion?

A useful reply names a number, a method, a personal experience, or a concrete example. If you could replace your draft with "I agree" and lose nothing, rewrite.

Have I read the top 3 comments already on this thread?

If the highest-upvoted reply already says what you were about to say, your comment will sink. Add what's missing — counterexamples, edge cases, the next step — not what's there.

Would my reply still work if my username was removed?

If it only makes sense because it promotes you, your product, or your platform, this sub will spot it. Frame the value as "this solved it for me," not "check out my…"

Did I skim the sidebar rules one more time?

Every sub has at least one rule that surprises outsiders — peer-review only, no images, no specific tags, no off-topic. Five seconds in the sidebar can save you a removal.

Want to draft this reply with the rules already baked in?

Try Redimates — free, 10 replies / week