Expert attention map

The Who's Who of AI

What credible people across AI noticed, why it matters, and where the field is converging or disagreeing.

2,397 searchable experts 4,280 tracked across all sources
Build my stream Create my edition
Filter the conversation Who is saying what?

Combine a professional role with a reaction lens. Both must match the same attributed contribution.

Clear all
Active evidence filter

Showing developments with attributable Building & implementation reactions.

New Network reaction maps

See how experts are reacting—not just what they shared.

Posts are grouped by conversation and tone. Select a lens to filter the stream; these are never permanent labels on people.

Building & implementation
0 live reaction maps in this view

No development in this filter has enough independent reactions yet. The maps appear as soon as the evidence supports them.

Debated

The questions experts are actively pulling apart

One card per development. Sources are clustered; reaction bundles describe these posts, never the people behind them.

No developments match these filters yet.

Try the field-wide view or clear one of the filters.

Clear filters
More conversations

What experts are discussing without an anchoring article

5 experts · 39 posts · 1d ago
Ed Zitron SE Gyges Doll Nafnlaus 🇮🇸 🇺🇦 mackuba.eu
Matches Building & implementation
“it's actually just that my posting history for the last hour right now is a litany of horrors that depresses me and i'm trying to avoid building the pile higher” evidence ↗
Multiple readings Policy & governance · 1 Opportunity & adoption · 1
SE Gyges: trying to deduce why one would quit a good job at anthropic
SE Gyges: what her boyfriend is up to today. they really do get around
Open the thread →
2 experts · 5 posts · 1d ago
Ramon Astudillo Marco Z
Matches Building & implementation
“I am missing a good KV-cache-friendly workflow that goes from Specs to closed PRs. Yeah it should be Specs -> Commits/Tags <-> PR but in reality it is Specs -> C/T <-> improve Specs -> C/T <-> PR R…” evidence ↗
Ramon Astudillo: I am missing a good KV-cache-friendly workflow that goes from Specs to closed PRs. Yeah it should be Specs -> Commits/Tags <-> PR but in reality it is Specs -> C/T <-> improve Specs -> C/T <-> PR R…
Marco Z: so you either reuse the cache or use current data. Can't have both 🥶
Open the thread →