explainx / blog
HashiCorp founder Mitchell Hashimoto (Vagrant, Terraform creator) warns entire companies are in AI psychosis, unable to have rational conversations about coding agents. Developers report vibe coding fatigue after 1 year with Cursor—tangled codebases, burnout, and the painful reality of maintaining AI-generated code.
Apr 27, 2026
Social feeds show ambitious builders 'fully cooked' by mid-afternoon despite AI leverage. Token spend surges 13×, context switching exhausts cognition, and vibe-coded apps collapse under their own weight. Here is the paradox, the economics, and the escape hatch.
Jul 17, 2026
Every agent-generated landing page looks the same because models share the same training defaults. Hallmark encodes anti-slop rules — structural variety, honest copy, locked tokens — and ships as a SKILL.md for Claude Code, Cursor, and Codex. Here's what it does and how to install it from explainx.ai.
Jul 17, 2026
Cursor ML lead Lee Robinson's AI Engineer stage talk is now live — recursive model improvement via outer feedback loops and inner RL evals, SpaceX Colossus compute, textual feedback for credit assignment, and agents that train models from Slack. explainx.ai recaps the full transcript and X reaction.
On May 16, 2026, Mitchell Hashimoto—founder of HashiCorp and creator of Vagrant, Terraform, Vault, and other infrastructure tools millions of developers rely on—posted a stark warning: "I strongly believe there are entire companies right now under heavy AI psychosis and it's impossible to have rational conversations about it with them."
Within hours, the X post drew 987 responses from developers sharing war stories: vibe coding fatigue after 1 year with Cursor, tangled codebases that "baffle maintainers and demand rewrites," and the painful realization that AI-generated prototypes don't scale to production-grade software.
This isn't a Luddite rejection of AI tooling. Hashimoto himself uses AI coding tools. The warning is about companies losing the ability to reason about trade-offs—shipping fast but creating brittle systems, burning out engineers who can't explain their own codebases, and mistaking prototype velocity for sustainable engineering.
This post connects the dots: Hashimoto's AI psychosis warning, the vibe coding fatigue epidemic, Jeff Morris Jr.'s 3-month experiment proving AI can't build commercial mobile apps, and what rational AI adoption actually looks like for engineering teams in 2026.
AI psychosis (Hashimoto's term) is the organizational delusion where companies are so convinced of AI coding agents' productivity gains that they cannot have rational conversations about limitations, technical debt, or long-term maintainability. Symptoms include:
Vibe coding fatigue is the inevitable crash: developers exhausted from maintaining code they didn't write, can't explain, and struggle to debug when it breaks.
Why this matters now: AI coding tools (Cursor, Claude Code, GitHub Copilot) reached critical mass in 2025-2026. Early adopters are hitting the 6-12 month wall where initial productivity gains reverse into maintenance nightmares. Companies doubling down ("more AI!") vs sobering up ("we need senior reviews") are diverging paths.
Hashimoto's full X post (May 16, 2026):
"I strongly believe there are entire companies right now under heavy AI psychosis and it's impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out."
Mitchell Hashimoto isn't an AI skeptic yelling at clouds. His credentials:
When Hashimoto warns about companies unable to have rational conversations, he's describing organizations where:
Hashimoto compares AI psychosis to early cloud adoption mistakes:
AI coding parallel:
Hashimoto's prediction: Companies in AI psychosis will hit a reckoning when maintenance costs exceed velocity gains. The question is whether they course-correct or double down.
LiveOverflow (security researcher, 100k+ YouTube subscribers) posted May 16, 2026:
"my brain after one year of vibe coding" [image of exhausted developer]
The post got 72 🔥 reactions because thousands of developers recognize the feeling. After 6-12 months of using Cursor, Claude Code, or Copilot to generate code via prompts, reality hits:
Codebase incomprehension
Debugging paralysis
Maintenance dread
Cognitive exhaustion
Miguel Salinas (@Vercantez):
"Coming off of this psychosis and it's painful. Not shipping any more features until I can explain every part of our codebase in detail. Especially important to do before we open source."
Translation: Realized codebase is unmaintainable gibberish. Pausing features to rebuild understanding.
UI/UX Savior (@UiSavior):
"Designers before and after vibe coding.😎" [meme showing exhaustion]
Implication: Even designers (not just engineers) feel the burnout of rapid AI-driven iteration without quality checks.
Jeff Morris Jr. (Chapter One VC, ex-Tinder VP Product) ran a 3-month experiment: build a mobile app using vibe coding (Cursor, Claude, natural language prompts). His conclusion (X, May 16, 2026):
"We've spent 3 months building a mobile app. My verdict is you cannot vibe code a commercial-grade mobile product today. Mass-market apps still need very talented full-stack mobile devs."
What worked (prototyping):
What failed (commercial quality):
Specific failures reported:
Jeff's advice:
AI coding tools promised 10× developer productivity. Early adopters saw it: prototypes that took weeks now take days. But 6-12 months later, the productivity curve inverts:
The paradox: Tools designed to make coding faster make maintaining code slower when used without discipline.
Startups and VCs reward velocity:
Result: Companies optimize for demo-able features, ignore maintainability
Pre-AI learning path:
AI-era shortcut:
Result: A generation of developers who can prompt but can't code without AI
What execs see:
What they don't see:
Result: Doubling down on AI instead of course-correcting
Humans push back:
AI agents say yes to everything:
Result: Unchecked bad decisions compound into system-wide failures
Based on Hashimoto's warning and developer testimonials, here's how to use AI coding without losing your mind:
Rule: Every AI-generated file gets reviewed by senior engineer who must explain the architecture.
Why this works:
Implementation:
Hashimoto's advice (paraphrased from similar contexts): Developers should regularly read core codebase files to maintain understanding.
Practice:
Why this prevents psychosis:
Anti-pattern:
Better approach:
Example:
Balance:
Why:
Pre-AI: Design doc → peer review → code → review → ship
AI era shortcut: Prompt → code → ship (no design)
Rational approach:
Result: AI speeds up implementation, humans ensure soundness
Internal tools (used by <10 people, not mission-critical)
Prototypes (throw-away code for testing ideas)
Boilerplate (repetitive CRUD, API wrappers, tests)
Learning and exploration (experimenting with new tech)
Production apps at scale (fintech, healthcare, social, SaaS)
Mission-critical systems (payments, auth, data pipelines)
Code you'll maintain for years (core platform logic)
Team onboarding (teaching juniors to code)
Based on Hashimoto's warning and current trends:
Q: Is Mitchell Hashimoto anti-AI? No. Hashimoto uses AI tools. His warning is about irrational adoption—companies losing ability to reason about trade-offs, not AI tools themselves being bad.
Q: Should I stop using Cursor / Claude Code / Copilot? No. Use them intelligently: boilerplate, learning, prototyping. But always review, test, and ensure you understand the code before shipping.
Q: How do I know if my company has AI psychosis? Warning signs: (1) Can't have rational conversations about AI limits, (2) Maintenance backlog growing but leadership celebrates velocity, (3) Engineers burned out but told to "use AI more," (4) Questioning AI code quality = career risk.
Q: What's the difference between AI psychosis and AI enthusiasm? Enthusiasm: "AI helps us ship faster, let's use it wisely with reviews and tests" Psychosis: "AI makes us 10× productive, anyone who questions it is a dinosaur, ship everything the AI generates"
Q: Will AI coding get better and solve these problems? AI will improve (better reasoning, fewer bugs). But fundamental problems remain: AI doesn't understand business context, can't make trade-off decisions, and won't push back on bad ideas. Human judgment always required.
Mitchell Hashimoto's warning isn't "don't use AI coding tools." It's "don't lose the ability to think critically about what you're building."
AI coding agents (Cursor, Claude Code, Copilot) are powerful tools. But like any tool, misuse creates problems:
Vibe coding fatigue is real. LiveOverflow's "my brain after one year" post resonates because thousands of developers are hitting the same wall. The solution isn't abandoning AI—it's using it with discipline.
Next step: Audit your last 10 PRs. How many AI-generated files can you fully explain? If <80%, you're accumulating debt. Fix now before maintenance crisis hits.
Related reading:
Sources:
