On 2 February 2025 Andrej Karpathy floated "vibe coding": steer an AI with intent, accept a lot of generated code, and stop obsessing over every line like a medieval scribe.
Three days later the phrase already feels sticky. It names something people were doing quietly with copilots and agents.
What the vibe is
You describe outcomes. The model writes. You run it. You nudge. Reading becomes sampling, not line-by-line ownership.
Where it breaks
Prototypes love vibes. Production hates unread security holes, silent logic bugs, and dependency rot. The danger is mistaking speed for understanding.
This week is the term's birth certificate, before vendors turn it into a plan tier. Pair it with older nerves about programmers and AI and whether models write most of the code.
Teams should treat the vibe as a draft mode with mandatory review, tests, and a human who can still explain the control flow. Naming the practice helps. Worshipping it does not.
February is for vocabulary. March will be for scars.
Brak komentarzy:
Prześlij komentarz