02 — Discord & Slack: Real-Time Practitioner Chats

Real-time chat is where you get a helpful answer in 5 minutes at IST 22:00 while everyone in Bangalore is asleep. Verified July 2026.

The four you should join

1. #include <C++> Discord — the welcoming inclusive C++ community

  • Invite: http://includecpp.org/discord (official, redirects to a fresh Discord invite; the organization operates the invite so it stays live).

  • Website: https://www.includecpp.org.

  • Members: ~15,000 (2026).

  • Character: Explicitly inclusive, welcoming, moderated to keep tone civil. Beginners are actively welcomed. Recurring “office hours” with well-known C++ speakers.

  • Key channels:

    • #help — language questions, code help.

    • #beginner-help — gentler onboarding for beginners.

    • #showcase — share your project.

    • #job-postings — semi-active, some remote-friendly listings.

    • #committee-discussion — WG21 chatter, lurk to learn.

  • Voice/video: Voice chats happen occasionally for pair-programming.

  • India timing: Peak activity is EU/US = IST 18:00 – 04:00. Post questions before you sleep; expect answers in the morning.

  • Verdict: Join day 1. The friendliest high-quality C++ community online.

2. CppLang Slack — the standardization-adjacent Slack

  • URL: https://cppalliance.org/slack — self-serve email invite. You get an invite email in a few minutes.

  • Operated by: C++ Alliance (nonprofit).

  • Members: ~15,000 registered, ~2,000–4,000 typically active.

  • Character: More serious/technical than the #include<C++> Discord. Many WG21 committee members read/post. This is where CppCon logistics chat lives too.

  • Key channels:

    • #learn — welcoming to beginners. Highly recommended.

    • #c++ — general.

    • #committee — WG21 chatter. Lurk.

    • #job-offers — sporadic but higher-signal listings than most job boards.

    • #cppcon — conference logistics, session hallway chat.

    • #meetingcpp — similar for Meeting C++.

    • Individual library channels: #boost, #pytorch (small), #llvm.

  • India timing: Same as Discord — EU/US peak = IST 18:00–04:00.

  • Verdict: Join day 1. Post in #learn when you have specific questions. Complementary to the Discord — the Slack has more standardization-adjacent voices; the Discord has more welcoming beginner tone. Have both.

3. Together C & C++ Discord (TCC++)

  • Invite: https://discord.com/invite/tccpp

  • Members: ~63,000 (July 2026). Largest general C/C++ Discord.

  • Character: More casual, more student-heavy, slightly noisier. Some strong opinions and gaming-C++ subculture.

  • Key channels: #c++-general, #help, #projects, #books-and-resources.

  • Verdict: Optional. Join if you like a larger community; skip if you’re #include<C++> + CppLang Slack. TCC++’s biggest strength is 24-hour coverage from its huge global membership — questions posted at IST 02:00 are usually answered.

4. C++ Discord (discord.gg/cpp)

  • Invite: https://discord.com/invite/cpp

  • Members: ~13,600.

  • Character: Similar to TCC++ but smaller.

  • Verdict: Skip. Redundant with #include<C++> and TCC++.

Adjacent Discords worth joining (Phase 5+)

PyTorch official Discord

  • Invite: search “PyTorch Discord” on https://pytorch.org — the invite link is listed in the PyTorch community pages. Discord invite links rotate; use the pytorch.org current link.

  • Members: ~10,000 (mid-2026).

  • Character: Half users, half framework developers. #compile, #internals, #libtorch channels are relevant to a C++/ML target.

  • Verdict: Join in Phase 5 when your libtorch-adjacent work starts.

MLOps Community Discord

  • Invite: https://mlops.community/join/

  • Members: ~20,000+.

  • Signal: Very ML-industry-focused. #inference-optimization and #gpu-serving channels touch on C++/CUDA workloads.

  • Verdict: Join in Phase 5–6 for career-adjacent signal.

Rust Discord

  • Invite: https://discord.gg/rust-lang (from the Rust community page).

  • Why relevant: C++ vs Rust conversations are frequent; you’ll want first-hand Rust community context (not just “C++ is doomed” hot takes). Cross-language perspective sharpens both.

  • Verdict: Optional lurk. Not required for C++ path.

LLVM Discourse (replaced IRC)

  • URL: https://discourse.llvm.org

  • What it is: LLVM/Clang/LLDB community forum, replaced the legacy cfe-dev and llvm-dev mailing lists in 2022. All Clang/LLVM discussion, RFCs, and bug triage happens here.

  • Character: Compiler-writer-adjacent, very technical. Lurk.

  • Verdict: Reference only. Post here only when you’re contributing to LLVM (Phase 6+ stretch goal).

Anti-patterns

  1. Random “C++ crash course” Discords that appear in YouTube tutorial descriptions. Usually run by a single YouTuber; low-signal, self-promotional, transient. Skip.

  2. Telegram / WhatsApp “C++ study” groups. See prior file. Skip.

  3. Discords with more members than moderators. TCC++ works despite its size because it’s well-moderated. Random 5000-member “programmers” Discords are usually not.

How to use these chats effectively (India context)

  1. Set your Discord/Slack timezone to IST so message timestamps are local. Settings → Language & Region.

  2. Post questions before you sleep (IST 22:00–23:00). Answers land in your morning. This is the single biggest quality-of-life hack for India-based engineers using Western-timezone communities.

  3. Provide a godbolt link with your question. A godbolt.org snippet reproducing the issue in 20 lines gets 10x more responses than a paste of code.

  4. Give an answer for every 3 you receive. Once you can answer questions (from month 4+), a rhythm of teaching accelerates your own learning more than any book.

  5. Do not DM strangers with questions. Post in the public channel. This is a Discord/Slack cultural norm. DM’ing a known expert with a language question is a fast way to get soft-blocked.

Priority order (final)

Day 1: #include<C++> Discord + CppLang Slack. Phase 5: PyTorch Discord + MLOps Community Discord. Optional lurks: TCC++, Rust, LLVM Discourse.