AI Could Drain the Shared Expertise Pool Professions Need to Survive
The Tragedy of the Cognitive Commons
This conceptual paper introduces the Cognitive Commons framework, which combines commons theory, HRD scholarship, and distributed cognition to explain how rational AI adoption can deplete the shared expertise that professions rely on for renewal. It distinguishes Internalized Mastery from Distributed Mastery and introduces the Validation Tether, which shows that effective AI oversight depends on the very expertise AI may undermine. Early evidence from labor markets and clinical settings suggests disruption to expertise-regeneration pathways in AI-exposed sectors, and the paper identifies five factors that determine occupational vulnerability, proposing governance across organizational, professional, and policy levels.
Effective AI oversight depends on the expertise AI adoption may undermine.
- io84
A new and growing fear I have is that AI cuts off some of the most well-trodden pathways to intellectual growth. Every time the AI solves a problem that I would not have been able to efficiently solve alone, it has replaced an interaction that previously would have happened with a mentor/supervisor/code reviewer. This is faster for the person seeking the micro-assistance, but there is a flipside: fewer human-to-human acts of mentorship and shared problem solving. We lose a lively ingredient of team formation, expert formation, and a source of joy for all involved. As this scales up it feels plausible that we end up with a wider deagradation of intellectual standards. I like the Cognitive Comons framing.
- xendo
For anyone that does LLM supported work it's crystal clear that skill decline is real. Surprisingly, the leadership at my work doesn't give rats ass about it. They published AI engineering manifesto, pushing for loops, workflows, advocating for producing many times more code. All of this ignoring the elephant in the room.
- cadamsdotcom
We will look back on this era as one of transition. AI is in its "look monkey can do tricks how cute" era - but it won't be long. For instance the era of "whoa" is happening right now in mathematics (Anthropic researchers are pushing math's frontier with little more than the prompt "you can do it" - ie. brute force), and in coding agents we're crossing over - look into leading-edge benchmarks like SlopCodeBench that are pushing labs to RL for long term codebase health and not just problem-solving. The reason I say coding agents will go in this direction is labs are competing to have the most appealing models and so seeking out new unsaturated benchmarks they can hill-climb and show flashy results from, demonstrate to customers they're the best and deserve spend.
What these cognitive tools do is make the mundane work we're lamenting the loss of redundant. Who cares if junior devs can't code? When this stuff really gets going they'll be using their answer boxes to both code AND to have have design discussions with a form of intelligence that has every PhD ever obtained and infinite patience.
Consider: long division used to be in school curricula; our forebears had to know it to be considered "educated"; and yet I, in my 40s, was never taught long division.
Where did it go?
- culebron21
Similar to the argument made by John Blow several years ago. Though, Blow blamed frameworks/engines and layers of abstractions. I wonder if the authors came to this framing themselves, or listened him.
- jmfldn
My approach is to write a bit of totally AI-free code every day. So after a day of Claude, I'll spend at least 30 mins wrestling with something. The gnarlier the better, e.g.leet code or Project Euler-type stuff. I think of it as like lifting weights for the mind. The more I struggle at the edge of my knowledge and skill the better.
The other thing is to give your agent a skill not to solve certain key problems unless explicitly prompted. Write the scaffolding sure, but leave the juicy parts alone. And if I get stuck, I have it enter into a dialogue with me, nudging me towards understanding.