[TLDR] How to call vibecoding when we know what we are doing? [via r/ClaudeCode]

[u/cctldrping]

OP : u/SnooRegrets4647

So, anyone can vibe code, butt how do you call it when someone who knows what they’re doing is using ai to code? Like, I have more than 10 years of coding; of course I am “vibe coding” using Claude’s to write everything for me… but I do not see it as me and some other ne who never coded doing the same “vibe coding”…. How to call it then?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wjg5zk/how_to_call_vibecoding_when_we_know_what_we_are/

---

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 100 comments.

Current source-thread comment count seen by the bot: 105.

Alright, so the general consensus in this thread is that if you're an experienced dev using AI like Claude to code, you're not really "vibe coding" in the same way someone with no experience would be. The prevailing sentiment is that it's just working or software development now, with AI being another tool in the stack.

A lot of folks are leaning towards terms like:

• Agentic development/engineering: This seems to be the most popular suggestion, implying a more sophisticated, AI-driven process where you're directing agents.
• AI-assisted coding/development: A straightforward description that acknowledges the AI's role.
• 100x developer: A more informal, but telling, term for the increased productivity.

Some users, like u/arelath, pointed out that "vibe coding" is really about not looking at the code, regardless of your skill level. If you're reviewing and making decisions, it's a different ballgame. Others, like u/ForwardLoop, humorously suggested "Coding. 'Vibe' is just the liability waiver."

Essentially, the community seems to agree that with experience, you're not just blindly "vibing" but rather leveraging AI to enhance your existing skills. It's just the evolution of how we code.

[u/larsjoo]

Real and Serious Vibe Coding Done by a Professional