Full disclosure: I help manage AI products for my company, which also involves helping engineers use AI tools more effectively. I think of the act of using an

Full disclosure: I help manage AI products for my company, which also involves helping engineers use AI tools more effectively. I think of the act of using an LLM's assistance to produce code as two distinct actions, depending on who's doing it: * Amateurish efforts, by someone who doesn't really understand or care about code quality. This is "vibe coding," where the LLM is doing maybe 95% of the work. Back in the day, the pejorative term "script kiddies" was used to describe would-be hackers who basically just ran scripts written by others, rather than developing their own skills. And those are the sorts of people I would describe nowadays as vibe coders. * Judicious use by someone who knows what they're doing and just wants to move faster. Rather than letting the LLM do 95% of the work, it's more like a pair programming session, where the "senior" developer remains in the driver's seat but lets the "junior" LLM handle smaller, well-defined tasks that can be easily reviewed for quality.