Keeping up without drowning

Why it feels urgent

The volume is enormous and it is not slowing. But notice the mechanism behind the feeling: launch announcements are written to feel urgent, and the person posting is rewarded for your attention rather than for your career. Your sense of falling behind is the product being sold, and it is sold by people with model releases, courses and newsletters to promote.

Once you can see that, the noise becomes much easier to ignore without guilt.

The three-source rule

Pick three sources you actually read, and let everything else reach you by accident.

• One primary. The documentation and release notes of the tools you actually use. Model provider docs. The paper, when there is one, rather than the thread about the paper.
• One practitioner. Somebody who ships things and writes about what broke. Their failures are worth ten launch posts.
• One local. Your country’s or language’s community, because hiring, pay and regulation are local and the global feed will never tell you about them.

Three. Everything else you sample quarterly, which is often enough for anything that survives a quarter.

The test for whether something matters

Would this change a decision I am making this quarter?

If no, note the name and move on. You can learn any tool in a week when it becomes relevant to you. You cannot recover the six months spent skimming announcements about tools you never used.

This rule feels reckless the first time you apply it and is almost always right. The important developments do not disappear; they keep appearing, in your primary sources, attached to problems.

What is worth tracking

Four things, because they change decisions rather than opinions:

• Prices. They fall unevenly and they change build-versus-buy arithmetic. A feature that was uneconomic last year may be trivial now.
• Context limits and capability changes in the models you actually build on.
• Deprecations. This one bites hardest and gets the least attention: a provider retiring a model version breaks an application that has run untouched for a year. Providers publish deprecation schedules; check them for anything you have in production, and diarise the dates.
• Licence changes on open models and libraries. An open weight model whose licence changes can make a shipped product non-compliant overnight.

The half-life argument

Some knowledge decays fast and some barely decays.

Fast: the API surface of a specific framework, the current best model, the fashionable orchestration library, prompt tricks tied to one model version.

Slow: SQL. Statistics. Debugging. Writing clearly. How data actually gets messy. Your domain: how insurance claims work, how a hospital admits patients, how freight is priced.

Nearly everyone spends their learning time on the fast-decaying half because it is what gets announced. Deliberately spending most of yours on the slow half is the entire strategy of this lesson, and after five years the difference between two people who studied equally hard is almost entirely this allocation.

A monthly routine that fits a working life

Two hours, once a month:

1. Thirty minutes: release notes and deprecation pages for the things you actually run.
2. Thirty minutes: one long-form piece or paper, read properly rather than skimmed.
3. One hour: build something tiny with one new thing. Not a tutorial: the smallest possible real use.

That is it. It sounds inadequate against the volume of what exists, and it produces more durable capability than daily skimming, because the hour of building is the only part that becomes knowledge.

The free path

Everything you need is free and primary: provider documentation, arXiv, model cards on Hugging Face, project changelogs, and the community for your language or region. The paid layer (newsletters, courses, video subscriptions) mostly repackages those sources with a delay and a personality attached. Some of it is good. None of it is where the information originates, and paying for it does not reduce the volume problem.

The limitation, stated honestly

This approach trades novelty for depth, and it will occasionally make you late to something real. You will hear about a important shift a few months after the people who read everything.

That is the correct trade for a career, and the cost is smaller than it sounds: the real shifts persist for more than a quarter, so they reach you anyway, at the point where they have stopped being speculation and started being something you can use.