technical-term · Operating model · practitioner · Reviewed

Vibe coding

A practitioner label for software creation driven primarily by natural-language iteration and observed behavior, often with limited attention to the generated code.

Definition

Vibe coding describes a highly exploratory mode in which a person asks a model to create or change software, runs it, and iterates from visible results. It can accelerate prototypes and learning, but consequential software still requires explicit intent, architecture, tests, provenance, security, ownership, and release evidence.

The phrase is culturally influential but informal, inconsistently defined, and not an engineering standard.

Why it matters

The mode is valuable when reversibility is high and the objective is discovery.

Agentic engineering begins where organizations make the surrounding intent, context, execution, verification, and accountability system explicit.

System anatomy

Natural-language steering
The person directs changes through conversation.
Rapid feedback
Visible execution drives the next request.
Low code inspection
The person may rely more on behavior than detailed implementation review.

Important distinctions

Agentic engineering
Agentic engineering treats the full delivery and control system as the engineering artifact.
Prototyping
Prototyping is a lifecycle intent; vibe coding is one informal interaction style.

Implementation signals

  • Keep use proportional to reversibility and impact
  • Convert discoveries into explicit requirements and tests before production
  • Do not hide generated-code provenance

Failure modes

  • Prototype assumptions reach production unexamined
  • The operator cannot explain, maintain, or verify the resulting system

Sources and further study

  1. Andrej Karpathy — Software Is Changing (Again)

    A thought-leadership lens on natural language, neural networks, and changing software interfaces—not a formal standard.

    Use in this library: Practitioner perspective. This is an attributed thought-leadership or practitioner source, not a consensus standard or independently validated general law.

    talk · video · Published 2025-06-17
  2. GitHub — Spec-driven development with AI

    A structured specification-to-plan-to-task workflow for making intent durable and actionable by coding agents.

    Use in this library: First-party case study. This first-party account documents one organization, product, or implementation context and should not be generalized without local evidence.

    engineering · engineering · Published 2025-09-02
  3. OpenAI — Harness engineering: leveraging Codex in an agent-first world

    A production case study in designing repositories, tools, feedback loops, and environments for agent-first delivery.

    Use in this library: First-party case study. This first-party account documents one organization, product, or implementation context and should not be generalized without local evidence.

    engineering · engineering · Published 2026-02-11