Where do Claude Code developers go now that r/programming banned LLM discussion?

Yesterday r/programming temporarily banned all LLM programming discussion. The thread hit 62 points on HN before the mods reversed it — but the signal is clear: the biggest developer subreddit is hostile to AI coding tools.

If you use Claude Code, Copilot, or any LLM for programming, you're increasingly unwelcome in the places you used to hang out.

So where does the Claude Code community actually live now?

The community fragmentation problem

LLM-assisted coding has split developer communities in half:

• Anti-LLM faction: r/programming, HN comment sections, senior dev forums
• Pro-LLM faction: scattered across Twitter/X threads, Discord servers, individual blogs

There's no central place. Which means power users building real workflows with Claude Code are sharing tips in DMs and private channels — while the public discourse is dominated by people arguing about whether AI coding is "real" programming.

What Claude Code power users are actually doing

Here's what I see in the communities that are working:

1. CLAUDE.md as project documentation

The shift that changed everything for complex projects:

# Project: auth-service

## Architecture
- Express + Passport.js + PostgreSQL
- JWT access tokens (15min) + refresh tokens (7day)
- All auth logic in /src/auth/, not scattered in routes

## Conventions
- Error handling: always use AppError class, never throw raw errors
- Logging: winston logger only, no console.log in production
- Tests: Jest, co-locate test files, 80%+ coverage required

## What NOT to do
- Never store tokens in localStorage (XSS risk)
- Never bypass the rate limiter middleware
- Never add dependencies without checking bundle size

This isn't just for Claude — it's your project's constitution. New team members read it. Claude reads it. Everyone works from the same mental model.

2. Hooks for automated quality gates

From the source leak (and now official docs), Claude Code has a hooks system that most developers haven't explored:

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Write",
        "hooks": [{
          "type": "command",
          "command": "node scripts/pre-write-check.js"
        }]
      }
    ]
  }
}

Your pre-write-check.js can:

• Verify the file path is within allowed directories
• Check if the file is in .gitignore before overwriting
• Log every file write to an audit trail
• Block writes to production config files

This is the kind of workflow tooling that advanced users are building — and almost nobody is talking about it publicly.

3. The ANTHROPIC_BASE_URL escape hatch

For developers who hit rate limits during long sessions:

export ANTHROPIC_BASE_URL=https://simplylouie.com/api
export ANTHROPIC_API_KEY=your-key
claude

This routes Claude Code through a proxy with flat-rate pricing. No per-token billing. No mid-session interruptions. SimplyLouie is $2/month — the whole point is removing the friction of watching your token budget during a 4-hour refactor session.

4. Slash commands for project-specific workflows

Create .claude/commands/ in your project:

# .claude/commands/review.md
Review the staged git changes for:
1. Security issues (SQL injection, XSS, secrets in code)
2. Performance regressions (N+1 queries, missing indexes)
3. Missing error handling
4. Test coverage gaps

Format output as: [CRITICAL] / [WARNING] / [INFO] with file:line references.

Now /review is a custom Claude Code command specific to your project. Every developer on the team gets the same review checklist. It's not AI replacing code review — it's AI making code review consistent.

Where the real discussions happen

Dev.to is currently the most tolerant developer platform for Claude Code content. The audience skews toward developers who build things rather than debate things.

Mastodon tech communities (fosstodon.org, hachyderm.io) are surprisingly engaged with Claude Code discussion — the culture there is more pragmatic than ideological.

Private Discord servers are where the real power-user discussions happen. If you're not in 2-3 active AI coding Discords, you're missing the fastest-moving conversations.

Build in public on LinkedIn — the developer audience there is less hostile to AI tools than Reddit, and the algorithmic reach is much better right now.

The opportunity in the fragmentation

The r/programming ban is actually a forcing function. It's pushing the pragmatic, build-focused Claude Code users toward platforms where they can have real discussions without getting dogpiled.

If you're reading this, you're probably already in that group. The question is where you want to build your knowledge base and community.

---

I write about Claude Code workflows and practical AI tooling. If you're looking for a flat-rate Claude API that removes rate limit interruptions during long sessions, SimplyLouie is $2/month.

What's your current Claude Code setup? Drop it in the comments — I'm collecting setups from power users.