[101008]

I did this analogy in the past and I was way downvoted. Just for clarification, I use vibe-coding a lot in side projects where I don't know if I am going to release it at all, or when I know that a mistake in the code won't crash a business.

However, when I do vibe-coding, I feel like a PM asking a remote team to do code and I get back the response asap. It could be good or it could be bad, but if I don't check it, I am just a PM trusting 100% what my engineer (team) did. How did this work in reality before IA? Well, the engineers had to have some kind of responsability and testing, and assuring that what they did was OK. Now that part is completely "disabled", and the PM Is responsable for the tech aspect as well, without the knowledge (and I am avoiding all the deploy / infra perspective).

[LauraMedia]

I may also just misunderstand the term itself. From what I've seen, "vibe coding" is used as a term for someone who does not want to go into the details, who does not want to check or adapt the code, who just wants to explain their idea to an LLM and expect a fully built feature, without doing any of the development themselves.

I myself use AI all the time, for smaller things, for more math-heavy things, for decisions I already thought about but want to check with best-practices (after all, LLMs are trained with the "hive mind" thoughts of programming). I use it as a companion, a tool akin to JetBrains refactor tools, something I can drop on a specific function to enhance my own work.