💡

Key Points

Key Takeaways

  • 1

    The Paradigm Shift

  • 2

    Clean Code is Dead?: If AI writes code, no need to write 'Cleanly' for human to read easy. It works is enough

  • 3

    Vibe Coding: Style to create thing that works 'Somehow (Vibe)' only with prompt and TAB key without caring about detailed implementation

  • 4

    Risk: Black-boxed code base. When bug occurs, 'AI Technical Debt' that no one can fix

  • 5

    Conclusion: Abandon Aesthetics, return to 'Hacker Spirit' creating thing that works muddily

Introduction: Farewell to Uncle Bob

When Robert C. Martin (Uncle Bob) wrote “Clean Code”, he did not assume. Future where “Subject writing code is not human”.

Naming convention of variables, length of functions, SOLID principles. These were all rules “To make it easy for humans to read and maintain”. However, what if AI writes and reads code? For whom is that rule?

1. What is “Vibe Coding”?

Concept advocated by Andrej Karpathy, former AI Director of Tesla. He used Cursor and Windsurf, and completed Python script “Without writing a single line”.

“I just write the prompt, hit Tab, and if it looks kinda right, I accept it. If it errors, I paste the error back to the AI. I don’t read the code. I just manage the Vibe .”

This is Vibe Coding. Care only “Whether it behaves as desired (Whether Vibe matches)”, not correctness of code. Implementation details are left to AI. Human is Manager, not Coder.

2. The Death of “DRY” (Don’t Repeat Yourself)

Iron rule of programming “DRY principle” is also ignored in Vibe Coding. Because for AI, generating similar code by copy and paste is easy (Zero cost).

Rather, creating independent by copy and paste is less likely to cause side effects when making AI fix, than increasing coupling by forcibly sharing. Paradox “WET (Write Everything Twice) is better for AI” is born.

3. The Risk: AI Tech Debt

However, Vibe Coding has fatal risk.

  • Code that no one understands : When bug occurs and AI cannot fix anymore, human will stand still in spaghetti code of tens of thousands of lines.
  • Security : AI may import vulnerable library arbitrarily.
  • Loss of learning : If junior engineer knows only Vibe Coding, becomes senior without knowing “Principle”.

4. How to Survive: Become “Vibe Manager”

Then, should we discard Clean Code? Answer is “Half Yes, Half No”.

If prototype or disposable script, should make with explosive speed with Vibe Coding. However, core system operating for several years (Payment infrastructure etc.) still requires Clean Code.

Skill of engineer polarizes.

  1. The Architect : Person who guarantees quality of code generated by AI and draws design.
  2. The Vibrator (Vibe Coder) : Person who makes thing that works fast anyway.

Conclusion: Love Chaos

Development site in 2026 is chaotic more than ever. However, it is also “Explosion of Creation”.

Let’s stop writing well-behaved code steadily. With partner called AI, create “Product changing world” with tremendous speed, muddily and dirtily. That is Hacker (Vibe Coder) of new era.

# ai # coding # vibe-coding # clean-code # essay # 2026