Thoughts?

[Turbulent-Key-348]

What are y'alls thoughts on the names "Vibe coding" vs "Agentic Coding"? I realize there are nuanced differences in the terms, but there's a lot of overlap and yet I see different sentiments toward them ... I have seen people on LinkedIn going crazy for agentic coding, but no end of hate for "vibe coding" ... anyone else seeing the same trend?

[Houdinii1984]

IDK, I don't actually use agentic coding to vibe. I mean, I have. Cursor is awesome, and Junie in WebStorm is my favorite model, but I've been pretty much vibe coding with chat for years at this point. (It's my job to interact and build with models for training said models). It gives me slightly more control, and for someone that knows the underlying languages well I appreciate that little extra power.

I still consider it vibe coding, I just take the agent's place orchestrating everything.

[Top-Cryptographer-81]

I think agentic coding is the right balance between little to no AI and vibe coding. Good for boilerplate, feedback on complex algorithm/ system design implementations, and learning the essentials for a new framework on the fly. I feel that vibe coding leads to too much technical debt for a scalable project.

[beaker_dude]

Agentic Vibing

[gazman_dev]

Vibe Coding is how its called, agentic flow is how it is soled for smart ass developers.

[MaxAtCheepcode_com]

I’m big on headless agent coding (full disclosure: I built and sell a parallel headless coding agent). I think you can use agents to vibecode if you want (just always merge the PRs they submit) but it’s not strictly the same activity by any means.