Skip to main content

Communities and Conferences

In one line: The signal is concentrated in a few specific places — AI Engineer Summit, Latent Space, a handful of Discords, and the engineering blogs of the major labs. Everything else is noise with occasional signal.

In plain English

You don't need to be everywhere — the useful conversations in AI engineering happen in a surprisingly small number of rooms. One practitioner-focused conference, one good podcast, a couple of Discord servers, and a handful of engineering blogs cover most of the real signal. The strategy this page teaches is depth over breadth: pick a couple of communities and actually participate, instead of lurking silently in twenty. Showing up consistently in a few places beats skimming everything.

1. Conferences worth tracking​

AI Engineer Summit / AI Engineer World's Fair​

The conference targeted at people who ship AI features (not researchers). Talks are practical: production systems, eval workflows, agent reliability, cost optimization. Run by Latent Space.

  • Why it's signal-dense: speakers are typically engineering leads at companies running real AI in production.
  • Watch the talks afterward: YouTube channel posts everything. Skim talk titles; watch the 3–5 that match your current problems.
  • Best track for beginners: the "stories from the trenches" / engineering case-studies tracks.

NeurIPS / ICML / ACL (academic)​

Research conferences. Papers are first-published here.

  • As an engineer: rarely worth attending live. Read selected papers afterward.
  • Workshops are sometimes more valuable than the main track — narrower, more applied.

Strange Loop (RIP / various successors)​

Historically a great engineering conference with strong AI tracks. Look for spiritual successors and regional analogs.

Provider-specific events​

  • OpenAI Dev Day — annual.
  • Anthropic events — less frequent, often virtual.
  • Google I/O — annual; AI announcements increasingly central.

These are mostly product launches but talks often include practical implementation guides.

Smaller, focused events​

  • MLOps World, MLOps Community events — production-ops focus.
  • Local AI meetups in your city — Bay Area / NYC / London have multiple per month; other cities have monthly or quarterly.

2. Podcasts that are actually signal​

Latent Space (swyx + Alessio Fanelli)​

The single best podcast for the AI engineer audience. Long-form interviews with people building production AI; deep dives on the architecture choices.

  • Cadence: weekly.
  • Format: 60–120 min interviews.
  • Backlog worth mining: episodes with Hamel Husain, Eugene Yan, Anthropic / OpenAI engineers.

The Cognitive Revolution (Nathan Labenz)​

Long interviews with researchers and founders. More breadth than Latent Space; less engineering-tactical.

Dwarkesh Patel​

Less AI-specific now but great when guests are AI researchers. Long-form, deeply researched interviews.

Hard Fork (Kevin Roose + Casey Newton)​

Mainstream-flavored but covers AI developments thoughtfully. Lower density of engineering signal; good for the broader landscape.

Last Week in AI​

Weekly news digest. Lower production value but high-signal aggregation.

3. Discords and chat communities​

The real-time AI signal is on Discord, not Twitter.

  • LlamaIndex Discord — RAG-focused; active developer community.
  • LangChain Discord — broader; can be noisy.
  • Hugging Face Discord — model-focused; great for open-weights questions.
  • Anthropic Discord — Claude-specific.
  • OpenAI Developer Forum — official; slower than Discord but quality answers.
  • The various model-specific Discords (e.g., Mistral) — useful when you're using that ecosystem.
  • Local AI engineer Discords / Slacks — often invite-only; ask around.

The right strategy: join 2–3 communities relevant to your work; mute most channels; actively participate in the ones that match your problems.

4. Reddit subreddits​

Highly variable quality but occasionally useful:

  • r/LocalLLaMA — self-hosting / open-weights community; high signal, somewhat insular.
  • r/MachineLearning — academic-heavy; useful for paper discussion.
  • r/OpenAI, r/Anthropic, r/ChatGPT — mostly user-focused; some engineering content.
  • r/ArtificialIntelligence — broad; mixed quality.

Reddit's content half-life is short; don't bookmark threads expecting them to remain useful.

5. Newsletters that earn the inbox slot​

Newsletter overload is real. The ones worth subscribing to:

  • Latent Space — written companion to the podcast; weekly.
  • Import AI (Jack Clark) — weekly; mix of research and policy.
  • The Batch (Andrew Ng) — weekly; broader AI ecosystem.
  • AlphaSignal — daily; pure paper aggregation.
  • Ben's Bites — daily; consumer-AI focused, low signal for engineers but good for cultural awareness.

Most other AI newsletters are noise; unsubscribe aggressively.

6. Where the engineering blogs live​

Curated list of blogs worth a feed-reader slot:

  • Eugene Yan (eugeneyan.com) — applied AI engineering; eval guides; great architecture posts.
  • Hamel Husain (hamel.dev) — evals, llm production patterns.
  • Simon Willison (simonwillison.net) — daily commentary, often very high signal.
  • Chip Huyen (huyenchip.com) — book author; production AI thinking.
  • Anthropic, OpenAI, Mistral engineering blogs — see Papers worth reading.
  • The pgvector / Postgres AI blog ecosystem — for the retrieval side.

A feed reader (NetNewsWire, Feedbin, Miniflux) gets you these in one place without checking Twitter.

7. The "lurker first" strategy​

When you join a new community:

  1. Lurk for 2 weeks. Read the top threads. Understand the culture and what people actually post about.
  2. Answer easy questions when you can. Lower-status; high-trust-building.
  3. Ask one substantive question when you have something specific (not "how do I learn AI").
  4. Participate from there.

The fastest way to be ignored or downvoted is to show up day one with a beginner question that's been answered 1000 times.

8. Building your own network​

Beyond communities, the senior-engineer move is building a personal network:

  • Conference hallways — talk to 5 people per conference. Get their emails. Send a follow-up message.
  • Discord DMs — when someone posts something that resonates with your work, send a DM with a specific follow-up question.
  • Open-source contributions — fixing a small bug in a popular AI library gets you into the maintainers' radar.
  • Writing publicly — blog posts, even short ones, make you findable to people working on the same problems.

Networks compound. The conversations you had at the conference two years ago become job offers, collaborators, peer reviewers, friends.

9. The "don't network just for jobs" rule​

The networks that pay off are built on shared genuine interest, not transactional ask-for-jobs energy. Become useful to others in the field; the opportunities surface organically.

Specifically:

  • Help others debug their AI problems.
  • Share what you learn (without overstating).
  • Cite people whose work you build on.
  • Show up consistently in small ways.

10. The "be in 2 communities deeply, not 20 shallowly" rule​

It's tempting to join everything. Resist. Pick:

  • 1 conference you attend annually.
  • 1 podcast you listen to consistently.
  • 1 Discord/Slack you actively participate in.
  • 5–10 blogs you read regularly.

This is sustainable. The "I'll keep up with everything" strategy is how you bounce off the field entirely.

Common mistakes​

Where people commonly trip up
  • Subscribing to every newsletter. Inbox overload; nothing actually read. Curate ruthlessly.
  • Joining 10 Discords and being silent in all of them. Pick 1–2 and participate.
  • Skipping conferences because "they're for senior people." Conferences are where you become senior. Go as a learner; it's the fastest growth shortcut.
  • Treating Twitter as the primary source. Twitter is noisy; the signal-dense places are conferences, podcasts, focused Discords.
  • Networking only when job-hunting. The networks built reactively don't pay off the way long-term genuine ones do.
  • Lurking forever. Sustained silent consumption gets you knowledge but no relationships. At some point, post / answer / contribute.
🤔 Quick checkQuick check

→ Next: When to pivot — the signals that your current approach has hit its ceiling.