Comment by zx8080

8 days ago

> “Agentic engineering” feels like the response of engineers who use AI to write code, but want to maintain the skill distinction to the pure “vibe coders.”

If there's such. The border is vague at most.

There're "known unknowns" and "unknown unknowns" when working with systems. In this terms, there's no distinction between vibe-coding and agentic engineering.

My definition to "vibe coding" is the one where you prompt without ever looking at the code that's being produced.

The moment you start paying attention to the code it's not vibe coding any more.

Update: I added that definition to the article: https://simonwillison.net/guides/agentic-engineering-pattern...

  • What if you review 50%? Or 10%? Or only 1%, is it not vibe coding yet?

    Where is the borderline?

    • I think the borderline is when you take responsibility for the code, and stop blaming the LLM for any mistakes.

      That's the level of responsibility I want to see from people using LLMs in a professional context. I want them to take full ownership of the changes they are producing.

      7 replies →