I'm not the only one more exhausted at the end of a workday using AI than before; apparently there's a term for that now: Brain Fry.
-The Gallup numbers are out. 80% disengaged. The heaviest AI users burning fastest. Everyone calls it a crisis. I think they're looking at it wrong.
- --+Your brain is reconfiguring from intonation to orchestration. That is a fundamental rewiring of how your mind spends its day. Of course it hurts.
-
Makes sense. Your brain is reconfiguring from intonation to orchestration. That is a fundamental rewiring of how your mind spends its day. Of course it hurts.
For years, your work was about producing; you held the tool, you shaped the thing, you felt the weight of it. Now the tool produces on its own and your job is to direct, to judge, to say yes or no from a distance.
-But discomfort is not damage. Ask Arnold if he quit lifting because of discomfort.
+That hurts. That doesn't mean it's broken.
-The problem isn't that your brain is broken. The problem is that most people focus on the discomfort instead of looking forward through it. The key word is forward; not ahead, not onward, but forward. Direction with momentum.
+Ask Arnold if he quit lifting because of discomfort.
-When I'm on the move, I move. When the reconfiguration is happening, you have two choices: sit in the pain and call it burnout, or recognize it as growth and keep your eyes forward. One is a loop. The other is a ladder.
+Discomfort is not damage. A seed doesn't stay a seed. It cracks open, sends roots down, pushes a shoot up through the soil it used to be protected by. The cracking is painful. The soil used to be home. Now it's in the way. But the cracking is the point; it's not a malfunction, it's the mechanism.
-What It Looks Like
+The problem is that most people sit in the discomfort instead of looking forward through it. The key word is forward; not ahead, not onward, but forward. Direction with momentum. When you're on the move, you move. One direction is a loop. The other is a ladder.
-They start using Copilot or Cursor. The first week is magical; three times the output, half the typing. The second week, they notice they can't remember why they chose this architecture over that one. The third week, they're tired in a way sleep doesn't fix. By month two, they're wondering if they're a good engineer anymore or just good at prompting.
+Intonation is the craftsman's relationship to the tool: you hold it, you feel its resistance, you adjust by touch. That's what you're losing. The architect who used to know exactly where every load-bearing wall was because she drew them herself. The engineer who could feel when a codebase was getting brittle because he'd written every third file in it.
-That's not brain fry. That's formation.
+Orchestration is different. You don't play the instrument; you tell the orchestra what to play. You hear the result. You adjust. But your hands never touch the bow.
-A seed doesn't stay a seed. It cracks open, sends roots down, pushes a shoot up through the soil it used to be protected by. The cracking is painful. The soil used to be home. Now it's in the way. But the cracking is the point; it's not a malfunction, it's the mechanism.
+The fatigue you're feeling is the gap between those two modes. Your brain is still trying to do both at once. It can't. That's the friction. That's the heat everyone calls brain fry.
-So What Do You Do With It
+But friction is not fire. Heat from formation is different from heat from burning. A blacksmith doesn't call the forge a problem; the forge is the point.
--
-
- Name it. You're not fried; you're forming. The cognitive fatigue is real, but its cause is growth, not decay. When you call it decay, you treat it with rest and retreat. When you call it growth, you treat it with orientation: are you looking forward through it, or sitting in it? -
- Preserve the decision boundary. The most engaged engineers I know use AI for exploration; show me three ways to solve this, not execution. They make the decision. The AI provides options. The human owns the choice. This preserves agency and prevents the cognitive fatigue of endless evaluation loops. -
- Measure judgment, not output. If your metrics are lines of code and story points, AI will look like a miracle and you will quietly disengage. If your metrics are architectural quality, system maintainability, and team learning velocity, the picture changes. Good judgment can't be faked by an LLM. -
- Build for the human, not the machine. Every AI deployment should pass this test: does it make the human more capable or merely more productive? Capability compounds. Productivity extracts. The difference shows up in engagement scores within six months. -
Elijah called down fire from heaven. Then he prayed for death. The boldness and the cost arrived in the same chapter. That's what formation looks like when you're doing it right; the capacity expands and the exhaustion lands in the same breath. Most people stop at the exhaustion. They name it burnout, name it crisis, name it brain fry. They don't look forward through it to see what's forming on the other side.
-What I'm Building
+What's forming is a different kind of mind. Not faster, not more productive. More selective. More directional. A mind that doesn't produce the answer but recognizes the right one when it sees it. That's not a downgrade. That's a promotion with harder work and a bigger view.
-I'm building two things in parallel. Speckl, a compliance specification language where AI generates the spec but a human reviews and approves it before the compiler turns it into code. The human judgment is embedded as provenance; auditable, verifiable, part of the artifact. And a consultancy helping engineering leaders shift from extraction metrics to capability metrics.
+The most engaged engineers I know use AI for exploration, not execution. "Show me three ways to solve this" — not "write this function." They make the final call. The AI provides options. The human owns the choice.
-If your team is showing signs of what the industry calls brain fry; higher error rates, faster turnover, quieter standups; the fix isn't more training. It's a structural rethink of how AI and humans collaborate.
+This matters because the fatigue isn't from thinking harder. It's from the opposite: from evaluating without deciding, from reviewing without owning, from scrolling suggestions without choosing any of them. Endless evaluation loops are what drain you. The fix isn't to use AI less. The fix is to preserve the decision boundary.
--+The story is that your mind is doing something it has never done before, and that hurts, and hurting while growing is different from hurting while dying.
-
If you're just approving code you didn't write and don't fully understand, you're not orchestrating. You're signing off. There's a difference. One is a conductor reading every part. The other is a rubber stamp.
+ +If your metrics are lines of code and story points, AI looks like a miracle and you slowly disengage from the work that actually matters. If your metrics are architectural quality, system maintainability, and team learning velocity, the picture changes. Good judgment can't be faked by an LLM.
+ +Judgment is the skill that compounds. Output is the thing that extracts. The difference shows up in engagement scores within six months. It shows up in retention within a year. It shows up in architecture quality within two.
+ +The question every AI deployment should answer is simple: does it make the human more capable or merely more productive? Capability compounds. Productivity extracts. Strip-mining the soil yields a great harvest this season and a dead field the next.
+ +This is not a call to slow down. Speed isn't the enemy; directionless speed is. A team with healthy soil ships faster because the structure holds, not in spite of it.
+ +This also isn't about tooling. DevEx isn't about better editors or faster completions. DevEx is about whether anything actually gets used and whether the people using it are getting better or just getting faster. Who gives a crap about things that are never used.
+ +And this definitely isn't about managing token costs. Token anxiety is a symptom of directionless work. If you optimize for outcomes, token cost is meaningless because the outcome is always more valuable. The only reason to worry about tokens is when you don't know what you're doing.
+ +What this is about is a name for what's happening right now: fear-based development. Not anxiety, not stress. Fear. The word matters. Fear that you're being replaced. Fear that you're falling behind. Fear that the discomfort means you're broken. None of those are true. But naming the fear is how you stop letting it drive.
+ +The story is that your mind is doing something it has never done before, and that hurts, and hurting while growing is different from hurting while dying.
Forward is the direction. Not ahead. Not onward. Forward.
-Which way are you looking?
+That's what I've got. What's your take?