AI coding tools removed the friction that used to make you pause and evaluate your own work. The medial orbitofrontal cortex — the part of the brain that computes whether something is good — needs that friction. Without it, the quality-judgment circuitry goes quiet. Not tired. Quiet. The studies below show what that looks like across five independent research groups.
In April 2026, MIT Technology Review named the era: AI malaise.
You accept an AI suggestion. It looks right. You move on. But the part of your brain that used to pause and ask "is this actually good?" never got consulted. Do that a hundred times a day for a few months, and the neurons responsible for that judgment start losing their physical connections. Five independent research groups have now measured this from different angles.
METR randomized trial, 16 developers, 2025
MIT Media Lab EEG, cognitive debt pattern, 2025
BCG study, 1,488 workers, 2026
Stack Overflow Developer Survey, 2024 vs 2025
Stack Overflow Developer Survey, pre-AI vs 2025
The mechanism is specific. Arnsten (2009) showed that under sustained cognitive load, dendritic spines in the prefrontal cortex retract — the neurons that compute quality literally lose their branches. A vacation does not rebuild them. They only regrow when the brain gets occasion to practice the affected circuits under low-stress conditions.
Find any object on your desk — a pen, a mug, a paperweight. Something with texture and weight. Hold it in a precision grip (thumb against forefinger) while you read through the AI-generated code you're about to approve.
That grip activates the sensorimotor cortex, which shares a border with the medial orbitofrontal cortex — the region that computes quality judgment. When the sensorimotor cortex fires, it gives the mOFC an occasion to weigh in before the decision is already made. Most developers accept AI suggestions in under two seconds. The object in your hand creates a pause that lets the taste circuitry participate.
This costs nothing. You don't need our coin to do it. Try it for a week and see whether your relationship to AI output changes. If it does, the research below explains why.
The stat cards above show what. These papers explore why — from memory fragmentation and flow-state disruption to the emotional signature that code carries when no human actually wrote it.
The mOFC, dendritic spine retraction, and why AI coding tools silence the taste organ.
What flow state requires and why AI-assisted velocity breaks the preconditions.
Short-term memory fragmentation under AI suggestion load. The developer who forgets what they were building.
How code carries the emotional state of the person who wrote it — and what happens when no person wrote it.
Liston et al. (J. Neurosci., 2009) demonstrated that stress-induced dendritic spine retraction in the prefrontal cortex reverses completely within three to four weeks, provided the stressor is removed and the brain gets occasion to exercise the affected circuits. The spines regrow, connectivity restores, and the attentional set-shifting deficits that characterize burnout resolve.
What has remained open since 2009 is the practical question: in a working developer's life, what gives the mOFC that specific low-stress occasion to exercise? The free protocol above is a start. For people who want a structured daily practice designed around the neuroscience, that's what the coin is for.
See Full Results & Case StudiesThe free protocol above works with any object. The coin and the kit are for people who want to make it daily and structured.
Morning: a five-step activation stack inside the 90-minute adenosine clearance window — cold face splash, warm water in squat, sunlight walk, hero recall, implementation intentions — then you earn your coffee. Evening: 12–20 minutes of paired deactivation — warm foot bath with the ritual jar, catch-and-release visualization, two specific to-dos for tomorrow, cyclic sighs, sesame oil massage. The NFC chip gates each phase. Over 21 days the practice becomes autonomous.
NFC coin, Warm Ritual Jar, sand timer, USB amber light, sesame oil, and a protocol guide.
One exercise per day. Each day targets a different relationship between the coin and your work. By day 21 the practice is autonomous.
AM activation stack within 90 min of waking. PM deactivation in 12–20 min before bed. Each targets the same systems in opposite directions.
The conversation about AI's effect on developer cognition is happening in public. These are some of the voices driving it.
A literature review of the AI mandate — CEO statements (Pichai, Nadella, Lütke, Jassy, Amodei, Altman), worker testimony from Blind and Reddit, and the wellbeing programs that didn't catch it.