Vibe Coding¶
Type: Development methodology / AI-augmented building
Definition¶
Vibe coding is the practice of building software by describing your intent to an AI coding agent (Cursor, Codex, Claude Code, etc.) and reviewing/refining the output, rather than writing code line-by-line by hand. The term gained mainstream traction in mid-2026 and is associated with dramatically compressed development cycles — a "SaaS in a day" rather than weeks or months.
The Core Shift¶
| Traditional | Vibe Coding |
|---|---|
| Write code line-by-line | Describe intent, review output |
| Long dev cycles (weeks) | Short dev cycles (hours/days) |
| Developer-centric | Non-coder accessible |
| Off-the-shelf SaaS for internal tools | Build exactly to your workflow |
Key Characteristics¶
- Speed — Internal tools that previously took weeks can be built in hours
- Custom fit — Every feature is exactly tailored to the user's use case
- Low barrier — Non-engineers can build functional tools
- Codex/Cursor/Claude Code as the IDE — The AI does the typing, human does the directing
Relationship to dark-factory-kb¶
Vibe coding commoditizes the build step. This validates the dark-factory-kb thesis: if building is becoming free/fast, the remaining scarce skill is hosting and deployment. The hosting gap is the problem dark-factory-kb is positioned to address.
Risks / Failure Modes¶
From ai-delegation/failure-radius: vibe coding works well for bounded, reviewable tasks. It's dangerous when:
- The builder can't judge code quality (non-coder in production)
- Changes aren't tracked in version control
- No rollback capability when AI makes errors
Sources¶
- @baoskee tweet (June 10, 2026) — 251K views
- Industry adoption of Cursor, Codex, Claude Code as primary IDEs