A semantic history: How the term 'vibe coding' went from a tweet to prod

In 2025, the concept of "vibe coding," introduced by Andrej Karpathy, marked a shift in software development from traditional coding to a more intuitive, prompt-driven approach using AI, where developers describe their intentions, and AI generates the code. Originally a playful term for hobby projects, vibe coding's application to production systems raised concerns about the quality and reliability of AI-generated code, leading to an increase in incidents and outages. This transition exposed a gap in verification processes, requiring more rigorous oversight and scrutiny, especially as senior developers reported that the time saved by AI was often offset by the need for extensive code reviews. As a result, Karpathy redefined the concept as "agentic engineering," emphasizing the importance of maintaining software quality while leveraging AI's capabilities. The term's future and the working style it represents depend on addressing the quality issues of AI-driven development, necessitating the adoption of "vibe checks" as an industry standard to ensure AI-generated code's reliability and effectiveness.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.