EN 中文
← Blog

Wetware Upgrade

The ceiling of vibe coding isn’t AI — it’s biology.

Harvard Business Review recently published “When Using AI Leads to Brain Fry”, surveying 1,488 full-time workers. Finding: 14% of AI users experience what they call “AI brain fry.” I read it and thought — this is exactly what I’ve been living through. In my last post, I argued that the bottleneck eventually lands on the human brain. This HBR study confirms it’s not just me. It’s structural.

What AI brain fry looks like: mental exhaustion, a buzzing sensation, brain fog, difficulty focusing, slower decision-making, headaches, and the constant urge to stop and reset. Imagine fifty browser tabs open inside your skull. The primary cause: high-intensity AI supervision — monitoring multiple tool outputs simultaneously.

Vibe coding is, by definition, a high-cognitive task. Burnout isn’t a risk — it’s a guarantee. The question is how you manage it.

Hardware fixes. Since the bottleneck is biological, attack it biologically. Higher quality sleep and exercise — weight training plus cardio — are the highest-leverage resets. I also supplement daily: zinc and magnesium for nerve recovery and sleep, curcumin for inflammation, fish oil (Omega-3) as essential brain nutrition, and creatine for a slight energy boost. All safe, all evidence-backed. I’ve been on this stack since my gym days — stable, no issues. Diet matters too: cut the salt and grease. Mediterranean diet works best.

Software fixes. Reduce the number of decisions you make during development. The ideal: AI that can one-shot the entire task. The debugging loop is what really drains you. Invest in making your AI more capable — better scaffolding, better prompts, whatever it takes — and you reduce cognitive load at the root.

Don’t open too many sessions. I used to run nine terminals. Unnecessary. Two to three active development sessions is enough to keep most people fully loaded. Beyond three, you’re multi-tasking, and humans are bad at multi-tasking.

This is especially true at night. By evening, your brain’s context window is running low — decision quality drops off a cliff. You need sleep to compact. From my own data: coding at night produces significantly more bugs. Mornings don’t. Some of our cognitive mechanisms are remarkably similar to how LLMs work. Fascinating.

Pushing the ceiling of vibe coding requires biohacking.

湿件升级

Vibe coding 的天花板不是 AI,是生物硬件。

哈佛商业评论最近发了一篇 《When Using AI Leads to “Brain Fry”》,调查了 1,488 个全职员工,发现 14% 的 AI 使用者出现了“AI 脑烧”。看完我就一个感觉:这就是我过去几个月一直在经历的东西。上一篇我说过,瓶颈最终会落在人脑上。这篇 HBR 研究证实了这不只是个人感受,而是一个结构性问题。

AI 脑烧长什么样:精神疲惫、嗡嗡感、脑雾、注意力涣散、决策变慢、头痛,以及不断想停下来重启的冲动。就像大脑里同时开了五十个浏览器标签页。核心原因:高强度 AI 监督 — 同时监控多个工具的输出。

Vibe coding 本质上就是高认知任务。Burnout 不是风险,是必然。问题只在于怎么管理它。

硬件层面的修复。既然瓶颈在生物层,就从生物层进攻。更高质量的睡眠和运动 — weight training 加有氧 — 是最高杠杆的 reset 手段。日常补剂:锌和镁帮助神经恢复和睡眠,姜黄素抗炎,鱼油(Omega-3)是大脑的必需营养,肌酸略微提升能量。都是安全补剂,有充分证据支持。我从健身时期就在用,一直很稳定。饮食上也要配合:低盐低油,地中海饮食效果最好。

软件层面的修复。减少开发过程中的决策参与次数。理想状态:AI 能 one-shot 搞定整个任务。调试循环才是最消耗认知的环节。把精力投入到增强 AI 的能力上 — 不管是通过更好的脚手架还是其他手段 — 从根源上减少你需要做的决策。

不要开太多 Session。我之前同时开九个 Terminal,其实没必要。两到三个主力开发 Session 就已经够大部分人“吃一壶”了。超过三个本质上就是在 multi-tasking,而人类做不了真正的多任务并行。

晚上尤其如此。到了夜间,人脑的 context window 已经快耗尽,决策质量断崖式下跌。需要 sleep 来 compact。我个人数据的观察:晚上写代码 bug 明显增多,但早上就不会。人的某些认知机制和 LLM 高度相似,非常有意思。

提高 vibe coding 的上限,需要 biohacking。