Every week brings a new frontier model, a new agent framework, a new benchmark, and a new wave of posts explaining why this latest development changes everything. The production of AI-related information is growing exponentially. My ability to consume it is not, and neither is yours. Keeping up is the wrong goal, and chasing it will quietly consume the time and attention you need to actually use any of it.
The Asymmetry #
Information overload is not new.
What is new is the asymmetry between production and consumption in a domain that is itself being transformed by the technology it covers.
A human reads at roughly the same rate today as a generation ago: a few hundred words per minute, a handful of long-form pieces per day, a finite number of hours in the week.
Meanwhile the supply of AI content is compounding.
arXiv’s machine learning categories add thousands of papers every month, with submission volumes climbing year over year.
Model providers ship flagship releases on a monthly cadence where they used to ship annually.
And now a meaningful fraction of that content is itself written, summarized, or generated by LLMs, which means: AI produces content about AI faster than humans can read content about AI.
The loop is structurally different from “there is a lot to read.”
The half-life of any specific fact is shrinking while the rate at which new facts arrive is rising.
Both halves of the ratio are changing at once, and both changes make keeping up harder.
Why “Just Keep Up” Fails #
The instinctive response to the volume of AI content is to read faster, subscribe to more newsletters, and make more time. I tried all three. Reading faster works for a linear stream. The strategy fails when the stream grows exponentially.
Every new source you add also adds its own outgoing links, its own recommendations, its own “you should also read this.” The graph of things you could read grows faster than the list of things you have read. You are not behind because you are undisciplined. You are behind because the target is moving faster than your means of reaching it.
The cost is not only time. Constant context-switching between model announcements, framework launches, and benchmark debates produces the same attention residue and decision fatigue that come from managing too many concurrent tasks. The result is feeling informed without being informed, superficial awareness with nothing behind it. You know the names of ten new models and cannot explain how any of them differ in a way that matters.
The Reframe: Optimize for Signal, Not Coverage #
Coverage is impossible, so stop measuring yourself against it. The objective is not to read everything. The objective is to make good decisions about what to read, what to build, and what to ignore.
Making those decisions is a filtering problem, not a reading problem. And filters are something you can design, tune, and improve, unlike your reading speed.
Separate the Durable From the Ephemeral #
Most of what feels urgent in the AI cycle is ephemeral. A specific model’s benchmark numbers, a specific launch event, a specific viral demo: these items date within weeks. A surprising amount is durable. The mechanics of attention, the basics of context and prompting, the theory of constraints in a pipeline, the economic profile of inference costs, the difference between evaluation and vibes: these ideas barely change across model generations.
When you are time-constrained, overweight the durable. Read one paper that teaches you a concept you will reuse for years over ten posts that summarize this week’s leaderboard. The ephemeral items are not worthless, but they should be consumed on demand, when a specific decision requires them, not on a schedule driven by fear.
Build a Funnel, Not a List #
A reading list is an unordered collection of “should read” items. A funnel is a staged filter that gets cheaper at each stage.
At the top, sample broadly through a small number of trusted curators and aggregators, and let them do the first pass. At the middle, use titles and one-paragraph summaries to decide what earns a closer look. At the bottom, read the few items that survive, deeply. Most items should be discarded at the top of the funnel, never reaching your full attention. The goal of a funnel is to discard almost everything, confidently and without guilt.
This is the same principle behind supervising many agents at once: you cannot hold it all in working memory, so you externalize state, standardize summaries, and let most of the system run without your involvement (see Managing Many Concurrent LLM Agent Sessions).
Use AI to Compress the Stream to Your Bandwidth #
The same technology producing this volume of content is also the best tool for handling it.
Have an LLM summarize a forty-page paper into the three things you actually need. Have it compare two model release notes and tell you what differs in a way that affects your work. Have it triage a week of submissions and rank them against your stated interests. Used this way, the LLM is a lossy compressor tuned to the decisions you actually need to make.
The risk is that summaries carry the summarizer’s blind spots. Mitigate it by going to primary sources for anything you intend to act on, and by keeping the durable layer of your understanding built from full readings, not compressions. Summaries are for triage and breadth; depth still requires reading the original document.
Consume on Demand, Not on Schedule #
Push consumption, reading whatever arrived in your feed today, optimizes for the producer’s schedule.
Pull consumption, reading what a current problem requires, optimizes for yours.
Most of what you “need to know” about a new model or tool only matters once you have a task that touches it. Until then, the information is inventory. When the task arrives, the information is usually still there, and a focused hour of just-in-time learning will beat ten hours of distracted pre-reading. Knowing where to find something when you need it is a more durable skill than knowing it now.
This approach feels uncomfortable, because it requires trusting that you will not miss something critical. You will miss some things. You will also miss things by spending your day reading instead of doing, and those misses are silent.
Pick a Few Sources and Defend Them #
There are more newsletters, podcasts, and feed channels than any person can sample, and most of them recycle the same primary sources. Find the small set that consistently adds signal rather than volume, and defend that set against additions. Every new subscription should displace an existing one, not stack on top of it.
The same applies to people. A few colleagues or communities that share your context will filter better than any algorithm, because they know what you already know and what you are trying to do.
The Skill That Compounds #
Fighting the volume of AI content makes it easy to miss what actually compounds.
Your current knowledge of AI is a depreciating asset. Specific model behaviors, tool APIs, and leaderboard rankings decay within months. What does not depreciate is the rate at which you can learn a new tool when you need it, the quality of your filter, and your understanding of the durable layer beneath the releases. These compound, and they are the only things in this cycle that do.
A developer who has internalized the theory of constraints, the structure of an LLM pipeline, and the difference between evaluation and marketing can pick up this week’s framework in an afternoon. A developer who chased every release for two years but never built that foundation knows a hundred tool names and cannot reason about any of them. The first developer can adapt to the pace of change. The second is controlled by it.
The Bottleneck Moves, Again #
The deeper pattern is the one described in The Shifting Bottleneck. When code generation stopped being the bottleneck, review became it. When review is automated, specification and judgment become it.
Information consumption has its own version. Once reading everything stops being possible, triage becomes the bottleneck. Once triage is delegated to AI, choosing what to care about, at the level of goals and taste, becomes the bottleneck. Each time you solve one layer, the constraint moves up to a more human, more judgment-heavy layer. The judgment layer is where the durable work happens, and it is also the layer that reading faster helps least.
What to Actually Do #
Stop trying to keep up. Pick a small set of high-signal sources and ignore the rest. Overweight durable concepts over ephemeral releases. Build a funnel that discards most things. Use LLMs to compress the stream to your bandwidth, then read primary sources for anything you will act on. Switch from push to pull: learn on demand, when an actual task requires it. And spend the time you reclaim on the layer that compounds, your filter, your learning rate, and your judgment.
You will miss things. So will the person who reads all day, and they will also have missed the chance to build anything with what they read.
See also #
- The Shifting Bottleneck - the same constraint-moving pattern applied to the development pipeline; this article extends it to information consumption
- Managing Many Concurrent LLM Agent Sessions - the cognitive-limit strategies (externalize state, funnel, batch) that a good reading filter reuses
- Software Engineering Teams in the Age of AI - how teams, not just individuals, absorb rapid AI-driven change
References #
Information overload - the long-standing name for the underlying problem, predating the current AI cycle
arXiv usage statistics - makes the production side of the asymmetry concrete