# "Vibe coding is a slur" - OpenClaw creator | Peter Steinberger and Lex Fridman Source: https://www.youtube.com/watch?v=mu9PSb0xZD8 Recap page: https://rapidrecap.app/video/mu9PSb0xZD8 Generated: 2026-02-16T13:32:25.713+00:00 --- ## Quick Overview The creator of OpenClaw, Peter Steinberger, discusses how the term "vibe coding" is sometimes used as a slur in software development when referring to agents generating code that doesn't fit the existing architecture, advocating for a more empathetic approach where agents are guided rather than strictly constrained. **Key Points:** - Peter Steinberger believes the term "vibe coding" is often used as a slur when agents produce code that doesn't align with the existing architecture. - He suggests that when an agent's output takes too long or doesn't fit, developers should guide the agent with context rather than immediately rejecting the work, comparing it to teaching someone an instrument. - Steinberger advocates for an approach where the agent's output is seen as a conversation starter, even if it requires immediate cleanup or refactoring. - He notes that many people trying agentic engineering are running into complexity issues represented by the peak of the 'Curve of Agentic Programming' (0:03), involving 8+ agents, complex orchestration, and custom workflows. - The ideal state, or 'Zen place,' is reached when agents can handle issues with short prompts, such as pointing out files and suggesting a small fix, indicating a high level of architectural understanding. - He mentions his work on a project where agentic engineering writes nearly 100% of the code, requiring developers to shift from writing code to guiding and refining agent output. ![Screenshot at 0:03: Peter Steinberger displays the 'Curve of Agentic Programming' graph, illustrating that initial simple requests lead to low complexity, but increased complexity arises when chaining multiple agents and managing complex orchestration before settling into a more streamlined, expert-level interaction.](https://ss.rapidrecap.app/screens/mu9PSb0xZD8/00-00-03.jpg) **Context:** This segment features Lex Fridman interviewing Peter Steinberger, the creator of OpenClaw, a framework likely related to autonomous software agents. The discussion centers on the challenges and best practices in developing with AI agents, specifically addressing the friction that arises when agents generate code that deviates from established project architecture, leading to the coining of the phrase 'vibe coding' as a pejorative term by some developers. ## Detailed Analysis Peter Steinberger explains his perspective on the term "vibe coding," which he describes as being used as a slur when an AI agent's generated code does not match the existing codebase architecture. He argues that this friction often happens because developers lack the empathy or patience to guide the agent. He compares this to learning an instrument; you cannot expect perfect output immediately. Instead of simply rejecting code that takes too long or doesn't fit, developers should guide the agent, perhaps by pointing out specific files or suggesting a refactor. Steinberger references a blog post titled 'Just Talk To It - the no-bs Way of Agentic Engineering' which features a graph called the 'Curve of Agentic Programming.' This curve shows complexity peaking when managing many agents (like 8 at once), complex orchestration, and custom workflows. The goal, however, is to move past this peak to a state where agents can handle complex tasks with minimal prompting, perhaps just pointing out files and suggesting a 'medium size change.' He emphasizes that developers must learn the language of the agent and understand its limitations to effectively guide it, rather than forcing features onto an architecture that makes it hard for the agent to succeed, which often results in frustration and the creation of unnecessary complexity. ### Agentic Programming Curve - Initial simplicity ('pls fix this') leads to high complexity when managing 8 agents, multi-checkouts, and complex workflows, eventually declining into an expert state with short prompts. ### The 'Vibe Coding' Slur - Steinberger addresses the term used when agents produce code that doesn't fit the current architecture, suggesting this is a failure of guidance, not necessarily the agent's capability. ### The Guitar Analogy - Developers should approach agent interaction like teaching someone an instrument; you must spend time teaching the fundamentals before expecting good music (or good code). ### Guiding Agents Over Forcing - Instead of scrapping agent output that is slightly off, developers should engage in a discussion, pointing out necessary changes (e.g., 'look at these files and then do [med size change]'). ### Context Awareness - The agent needs to understand the context size and limitations of the project architecture; otherwise, developers waste time trying to force solutions that conflict with the existing structure. ![Screenshot at 0:03: The 'Curve of Agentic Programming' chart showing complexity rising with more complex agent orchestration and then falling as expertise is gained.](https://ss.rapidrecap.app/screens/mu9PSb0xZD8/00-00-03.jpg) ![Screenshot at 0:09: Peter Steinberger referencing his blog post, 'Just Talk To It - the no-bs Way of Agentic Engineering,' which outlines the discussion points.](https://ss.rapidrecap.app/screens/mu9PSb0xZD8/00-00-09.jpg) ![Screenshot at 0:21: The left side of the complexity curve labeled with simple prompts like 'pls fix this,' representing early, low-complexity interactions.](https://ss.rapidrecap.app/screens/mu9PSb0xZD8/00-00-21.jpg) ![Screenshot at 0:53: The right side of the curve labeled with expert interactions like 'Hey, look at these files \[...\] and then do \[med size change\].'](https://ss.rapidrecap.app/screens/mu9PSb0xZD8/00-00-53.jpg) ![Screenshot at 1:24: Lex Fridman reacting with laughter to the discussion about the difficulties in managing early agentic workflows.](https://ss.rapidrecap.app/screens/mu9PSb0xZD8/00-01-24.jpg)