The Dispatch
Daily · Synthesized · Opinionated
engineeringWednesday, May 6, 2026·5 min read

Vibe Coding and Agentic Engineering Converge

The lines between vibe coding and agentic engineering are blurring, posing significant implications for software development and code quality

A close-up of a laptop displaying code in a dimly lit room with a coffee mug nearby.
Photo: Daniil Komov

The recent convergence of vibe coding and agentic engineering has sparked intense debate in the software development community. Vibe coding, a term coined by Andrej Karpathy, refers to the practice of using AI tools to generate code without human review, while agentic engineering emphasizes the use of AI agents to assist in coding, with human oversight and expertise. As AI coding tools become more reliable, the distinction between these two approaches is becoming increasingly blurred, raising concerns about code quality, maintainability, and responsibility.

What happened

The concept of vibe coding was initially met with enthusiasm, as it promised to democratize coding and make it more accessible to non-technical individuals. However, as the practice gained popularity, concerns arose about the lack of human review and oversight, leading to the development of agentic engineering as a more disciplined approach. Recently, Simon Willison, a prominent software engineer, expressed his concerns about the blurring of lines between vibe coding and agentic engineering, highlighting the need for a more nuanced understanding of these approaches.

The use of AI coding tools has become increasingly prevalent, with many developers relying on them to streamline their workflow. However, this has also led to a decrease in human review and oversight, as developers begin to trust the output of these tools without thoroughly examining the code. This trend has significant implications for code quality, maintainability, and responsibility, as it can lead to errors, security vulnerabilities, and other issues.

The convergence of vibe coding and agentic engineering is also reflected in the changing nature of software development. As AI tools become more advanced, they are able to handle increasingly complex tasks, reducing the need for human intervention. However, this also raises questions about the role of human developers in the development process and the need for a balanced approach that leverages AI assistance while maintaining human expertise and oversight.

Why it matters

The convergence of vibe coding and agentic engineering has significant implications for software development, as it highlights the need for a balanced approach that leverages AI assistance while maintaining human expertise and oversight. The lack of human review and oversight in vibe coding can lead to errors, security vulnerabilities, and other issues, which can have serious consequences in production environments. On the other hand, agentic engineering offers a more disciplined approach, emphasizing the use of AI agents to assist in coding, with human oversight and expertise.

The stakes are high, as the use of AI coding tools becomes increasingly prevalent in the software development industry. The need for a balanced approach that leverages AI assistance while maintaining human expertise and oversight is critical, as it can help to ensure code quality, maintainability, and responsibility. Furthermore, the convergence of vibe coding and agentic engineering highlights the need for a more nuanced understanding of these approaches and their implications for software development.

How to think about it

To navigate the convergence of vibe coding and agentic engineering, developers should adopt a balanced approach that leverages AI assistance while maintaining human expertise and oversight. This involves understanding the strengths and limitations of AI coding tools, as well as the importance of human review and oversight in ensuring code quality, maintainability, and responsibility. By adopting this approach, developers can harness the benefits of AI assistance while minimizing the risks associated with vibe coding.

+ Pros
  • Increased productivity and efficiency in software development
  • Improved code quality and maintainability through human oversight and expertise
  • Enhanced collaboration and communication between developers and non-technical stakeholders
Cons
  • Potential for errors, security vulnerabilities, and other issues if human review and oversight are lacking
  • Dependence on AI coding tools can lead to a lack of human expertise and oversight
  • Blurring of lines between vibe coding and agentic engineering can create confusion and uncertainty

How to think about it

To navigate the convergence of vibe coding and agentic engineering, developers should adopt a balanced approach that leverages AI assistance while maintaining human expertise and oversight. This involves understanding the strengths and limitations of AI coding tools, as well as the importance of human review and oversight in ensuring code quality, maintainability, and responsibility. By adopting this approach, developers can harness the benefits of AI assistance while minimizing the risks associated with vibe coding.

FAQ

What is the difference between vibe coding and agentic engineering?+
Vibe coding refers to the practice of using AI tools to generate code without human review, while agentic engineering emphasizes the use of AI agents to assist in coding, with human oversight and expertise.
What are the implications of the convergence of vibe coding and agentic engineering?+
The convergence of vibe coding and agentic engineering highlights the need for a balanced approach that leverages AI assistance while maintaining human expertise and oversight, ensuring code quality, maintainability, and responsibility.
How can developers navigate the convergence of vibe coding and agentic engineering?+
Developers should adopt a balanced approach that leverages AI assistance while maintaining human expertise and oversight, understanding the strengths and limitations of AI coding tools, and ensuring human review and oversight in software development.
Sources
  1. 01Vibe coding and agentic engineering are getting closer than I'd like
  2. 02Vibe coding and agentic engineering are getting closer than I’d like
  3. 03My Thoughts on Vibe Coding vs. Agentic Engineering
  4. 04Agentic Engineering vs. Vibe Coding