---
id: "concept-vibecoding"
type: "concept"
source_timestamps: ["00:05:41", "00:09:35"]
tags: ["ai-workflows", "developer-behavior", "anti-patterns"]
related: ["concept-production-comprehension-gap", "concept-taste", "claim-traditional-signaling-broken"]
definition: "The practice of prompting AI to generate code, iterating until it superficially works, and shipping it without ever building a mental model of the underlying logic."
sources: ["s14-job-market-reality"]
sourceVaultSlug: "s14-job-market-reality"
originDay: 14
---
# Vibecoding

## Definition

Vibecoding is the modern development anti-pattern where a user prompts an AI tool ([[entity-chatgpt-d14]], [[entity-claude-d14]], Cursor, Copilot), iterates rapidly based on surface-level feedback, gets a feature to a state where it *seemingly* works, and immediately ships it.

Crucially, **at no point during this process does the user stop to build a mental model of what is actually happening within the codebase.** The user relies entirely on the 'magic box' nature of the AI, optimizing for the path of least resistance.

## Why it feels good

- Highly productive at the individual level.
- Lets one person ship massive amounts of output.
- Removes the friction of comprehension, planning, and testing.

## Why it's destructive

Vibecoding completely bypasses the deep understanding required to maintain, scale, or debug software. Multiplied across every engineer in an industry, it produces:

- Unprecedented volumes of code.
- Unprecedentedly low levels of actual comprehension.
- A fragile, undebuggable ecosystem (see [[concept-production-comprehension-gap]]).

## Relationship to signaling

Because vibecoded output is indistinguishable from comprehended output at first glance, **shipping no longer signals expertise**. This is the core of [[claim-traditional-signaling-broken]] and the death of the standard 'build a portfolio' advice ([[contrarian-portfolio-advice-is-dead]]).

## The antidote

The deliberate cultivation of [[concept-taste]] through [[action-decelerate-for-comprehension]] and [[action-create-explanation-artifacts]].

## External validation

Widely recognized anti-pattern in the literature. arXiv grey-lit reviews note a speed-quality trade-off; skipped QA creates 'vulnerable developers' unable to debug their own systems. Microsoft BUILD 2025 explicitly warned vibe coding is *not production-ready* without architecture, testing, and security review.

## Counter-perspective

For pure prototyping or idea validation (MVPs), vibecoding can be appropriate — speed beats perfection. The danger is when prototype velocity habits leak into production environments without explicit gating.


## Related across days
- [[concept-vibe-coding-d10]]
- [[concept-vibe-coding-d16]]
- [[concept-vibe-coding-d25]]
- [[concept-dark-code]]