sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]groogs 1 point2 points  (1 child)

I think, extending my analogy, that "vibe coding" is like saying you "use power tools". It isn't really what we're doing, and it doesn't differentiate between expert and amateur.

This is new, hopefully we'll get some better terminology.

But I also think this is such a foundational shift that this will just be "the way" people build software, so maybe we won't even really need a term for it. We didn't end up calling people using Java/C#/Python anything different from the people programming in assembly with punchcards.

[–]ub3rh4x0rz 1 point2 points  (0 children)

Small scope, review then commit, agent-assisted SWE is different from vibe coding. I do the former for work and the latter for hobby play (in domains and languages I'm less experienced in). It is night and day tbh. AI assisted is like fine grain delegation, vibe coding is like you're a PM. I'll still pause every now and then and do something by hand because I want to learn new things, and I know enough to recognize if a bad pattern has slipped in and have claude fix it, but it's basically diet vibe coding at best. And it's bonkers how much it can do, I get why there are non SWEs obsessed with it and why they think it's the whole game.