My Blog

The Rise of Vibe Coding

In early 2025, Andrej Karpathy coined the term "Vibe Coding." It wasn't just a meme; it was a recognition of a fundamental shift in how software is built. For decades, the barrier to entry for software engineering was syntax—knowing how to speak the machine's language, whether it was C++, Java, or TypeScript.

Today, that barrier has dissolved. Vibe coding refers to the practice of writing code primarily through natural language prompts, relying on Large Language Models (LLMs) to handle the implementation details. You describe the vibe—the intent, the behavior, the outcome—and the AI handles the syntax.

But is this the end of the software engineer? Far from it. It is the evolution of the engineer into the architect.

The Workflow Shift: From Writer to Editor

Traditionally, the engineering loop looked like this:

Think about the logic.
Translate logic into syntax.
Type the code manually.
Debug syntax errors and logic bugs.

In the Vibe Coding era, the loop has changed:

Prompt the intent (System Design).
Review the generated implementation (Code Review).
Iterate on edge cases and constraints (Refinement).
Integrate into the larger system (Orchestration).

The "writing" phase has been compressed from hours to seconds. However, the "review" phase has become infinitely more critical. When you write code line-by-line, you build a mental model of its execution. When you generate code, you must reverse-engineer that mental model from the output. This requires a higher level of seniority, not a lower one.

The Epistemological Crisis: What is the Source of Truth?

Perhaps the most profound shift is philosophical. For 50 years, the "Source of Truth" was the source code. If you wanted to know how the system worked, you read the code.

In the Vibe Coding era, the source code is becoming a derivative artifact—compiled from natural language intent. This raises a dangerous question: If the code is generated and rarely read, is it still the source of truth?

We are moving towards a world where the Prompt and the Test Suite are the true assets. The code itself is just a transient intermediate representation, much like Assembly language became after C was invented. We don't read Assembly anymore; soon, we might not read Python or TypeScript either.

But this creates "Understanding Debt." If the AI generates a complex solution that works, but no human fully comprehends the specific implementation details, do we truly own our software? Or are we merely leasing functionality from a stochastic model?

The "Vibe Coding Hangover" and The Death of Apprenticeship

It's not all smooth sailing. The industry is currently grappling with the "Vibe Coding Hangover"—codebases built entirely by AI without sufficient human architectural oversight. But a deeper crisis looms: The Death of Apprenticeship.

Senior engineers are senior because they spent years debugging trivial errors, writing boilerplate, and understanding low-level friction. They built their intuition through struggle.

If Vibe Coding removes the struggle, how will the next generation build intuition? We risk creating a generation of "Prompt Architects" who can describe a skyscraper but don't know that concrete needs time to cure. The challenge for engineering leaders is no longer just shipping features, but artificially creating "gyms" where junior engineers can struggle safely to build muscle memory.

The New Core Competencies

If syntax is no longer the differentiator, what is?

System Design & Architecture: Understanding how components fit together is more important than knowing how to write a sorting algorithm.
Testing & Verification: Since generating code is cheap, the bottleneck moves to verifying correctness. Automated testing is no longer optional; it is the guardrail that makes Vibe Coding safe.
"AI Whispering": The ability to decompose complex problems into atomic, prompt-able tasks that an LLM can execute without hallucinating.

Conclusion

Vibe Coding hasn't killed coding; it has elevated it. We are moving away from being bricklayers to being site managers. The tools are more powerful, but the responsibility to build something that stands the test of time—and the responsibility to understand how it stands—remains ours.