01 — Online Communities¶

Most ML communities will waste your time. The ones listed here have a demonstrated signal-to-noise ratio worth the investment. The rule: lurk for 2 weeks before posting, search before asking, and bring code or a specific question — not “how do I get started.”

Reddit¶

Reddit ML communities range from genuinely useful academic discussion to “which laptop should I buy for deep learning” noise. Know which subreddit you’re in and why.

Subreddit	Subscribers	Signal Level	Best Use
r/MachineLearning	3.2M+	🔴 High (but gatekept)	New paper releases, research discussion, job posts. Lurk more than post. Mods are strict.
r/learnmachinelearning	528K+	🟡 Medium	Beginner-to-intermediate questions. Friendly. Search first.
r/LocalLLaMA	423K+	🟠 High (narrow)	LLM fine-tuning, quantization, local inference. Very active. Best place for GGUF/llama.cpp/vLLM practical advice.
r/mlops	65K+	🟠 Medium-High	Production ML, deployment, monitoring. Real practitioner discussion.
r/datascience	1.2M+	🟡 Medium	Career advice, applied data science. Less theory. Mix of signal and fluff.
r/deeplearning	180K+	🟡 Medium	General DL questions. Some quality, some “how do I become an AI researcher” posts.

What most people get wrong: They post questions instead of searching. r/MachineLearning has 10+ years of archived discussion. Your “novel” question has been answered in 2019. Use the search. Also: upvoted posts in r/learnmachinelearning are not necessarily correct — always verify with primary sources.

Discord Servers¶

Discord is currently the most active real-time ML community space. More informal than forums, faster feedback loops, better for niche technical questions.

Hugging Face Discord¶

Members: 50,000+
Invite: hf.co/join/discord
Signal: 🔴 High
Channels: #transformers, #fine-tuning, #diffusers, #peft, #datasets, #paper-discussions
Why join: Direct access to HF library maintainers. Bug reports get responses. New model release discussions happen here before anywhere else. Best place to debug transformers and peft issues.
Caveat: High volume. Use channel-specific threads.

EleutherAI Discord¶

Members: 20,000+
Invite: Find at eleutherai.org
Signal: 🔴 Very High (narrow)
Why join: Open-source LLM research. The people who built GPT-Neo, GPT-J, The Pile, and Pythia. Not for beginners. Read-heavy, post only with substance.
Caveat: Intimidating. Research-grade expectations. Lurk for at least a month.

MLOps Community Discord¶

Members: 12,000+
Invite: mlops.community
Signal: 🟠 Medium-High
Why join: Production ML deployment, feature stores, model monitoring, CI/CD for ML. Active practitioner discussion. Links to jobs.

Learn AI Together¶

Members: 43,000+
Invite: Searchable on Discord Discovery
Signal: 🟡 Medium
Why join: Broad community, beginner-friendly, multiple learning tracks. Good for accountability and study groups.

Yannic Kilcher’s Discord¶

Members: 15,000+
Signal: 🟡 Mixed
Why join: Paper discussions tied to his YouTube videos. Some genuinely smart people. But also lots of “explain ML to me” posts. Filter by channel.

fast.ai Discord / Forums¶

Forums (preferred): forums.fast.ai
Signal: 🟠 Medium-High
Why join: Best community for the fast.ai course ecosystem. Jeremy Howard occasionally participates. Excellent for practical PyTorch questions. Forums indexed by Google — your questions help others.

Twitter / X¶

The actual ML research conversation happens on Twitter/X faster than anywhere else. Paper authors post preprints, engineers share bugs and fixes, and debates about architectures play out in threads. This is where you see what practitioners actually think — not what they write in polished blog posts.

Researchers & Authors (must-follow for depth)¶

Handle	Who	Why Follow
@karpathy	Andrej Karpathy	GPT/Tesla/OpenAI. Rare but high-value posts on ML foundations.
@ylecun	Yann LeCun	Meta Chief AI Scientist. Controversial takes on LLMs. Stimulates thinking.
@goodfellow_ian	Ian Goodfellow	Deep Learning book author. GAN inventor.
@sebastianraschka	Sebastian Raschka	LLM training, practical ML. Posts actual code, actual benchmarks.
@cwolferesearch	Cameron Wolfe	Deep learning papers explained with clarity. Very high signal.
@kchonyc	Kyunghyun Cho	NLP/seq2seq researcher. Nuanced, academic perspective.
@fchollet	François Chollet	Keras author, ARC-AGI. Strong opinions on benchmarks and reasoning.
@thom_wolf	Thomas Wolf	HuggingFace CSO. Tracks open-source LLM ecosystem.
@giffmana	Lucas Beyer	Google Brain. Vision models, ViT, scaling. Technical threads.

Engineers & Practitioners (must-follow for applied work)¶

Handle	Who	Why Follow
@swyx	swyx	AI engineering, Latent Space co-host. Tracks AI engineering trends without hype.
@chiphuyen	Chip Huyen	MLOps, production ML. Author of “Designing ML Systems.” Real-world systems.
@eugeneyan	Eugene Yan	Applied ML at Amazon. RecSys, production systems, career.
@jeremyphoward	Jeremy Howard	fast.ai. Practical deep learning, biological ML.
@joelgrus	Joel Grus	Skeptic. “Data Science from Scratch” author. Python best practices.
@nrehiew	Neel Nanda	Mechanistic interpretability at DeepMind. Transformer internals.
@martin_gorner	Martin Görner	Google. TPU/Keras/practical training. Lots of code.
@clefourrier	Clémentine Fourrier	HF evaluation team. LLM benchmarking, leaderboards.
@rasbt	Sebastian Raschka	(also @sebastianraschka) LLM from scratch, training details.
@_akhaliq	AK	HF daily paper aggregator. Follow for paper digest, not analysis.

For Indian ML Context¶

Handle	Who	Why Follow
@kalyan_prasad	Various Indian practitioners	Search “ML India” on X for active community
@sanyambhutani	Sanyam Bhutani	H2O.ai. Indian ML practitioner, interviews ML engineers, practical content.

What most people get wrong: They follow the “celebrity” accounts (Yann LeCun, Sam Altman) who post opinion, not technical depth. The real signal is in the mid-tier practitioners — 5K-50K followers — who post actual training runs, actual failure modes, actual benchmarks.

LinkedIn¶

LinkedIn ML content is 80% “AI will change everything” reposts. The 20% signal is worth having a filtered feed for. Don’t engage with the fluff — just follow and filter.

Accounts worth following on LinkedIn (signal, not reach):

Chip Huyen — Production ML, career, systems
Sebastian Raschka — LLM training, Python ML
Jay Alammar — Transformer visualizations, NLP
Andrej Karpathy — Occasional technical posts
Sanyam Bhutani — Indian ML practitioner, technical interviews
Aurélien Géron — Hands-On ML author, practical DL

Use LinkedIn for: Job market intelligence, researcher career moves, company ML blog posts (the ones engineers actually wrote, not the marketing team). Not for learning content.

Slack Communities¶

MLOps Community Slack¶

Status: Active as of 2025. 20,000+ members.
Join at: mlops.community/slack
Signal: 🟠 Medium-High
Best channels: #jobs, #feature-stores, #model-monitoring, #mlflow, #kubeflow

Weights & Biases Slack (community)¶

Status: Active
Join: Via W&B community page
Best use: Questions about W&B integration, experiment tracking patterns

DataTalks.Club¶

Status: Active, 60K+ members
Join at: datatalks.club/slack
Signal: 🟡 Medium
Best use: MLZoomcamp study groups, career discussion, job posts

Community Engagement Protocol¶

Lurk first. Every community has implicit norms. Violating them marks you as a tourist.
Search before asking. Your question has likely been asked. Find it.
Give context. “My model doesn’t work” is not a question. “My validation loss plateaued at 0.45 after epoch 3 with LR=1e-4, batch_size=32, using Adam — here’s my code” is.
Contribute. Answer questions you know. Post your findings after debugging something.
Time-box. Set 30-minute limits on community browsing. It’s a tool, not a dopamine loop.

Return to README.md · Next: 02_newsletters_and_blogs.md