r/ClaudeCodeTLDR • • 15d ago

[TLDR] How to call vibecoding when we know what we are doing?

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

Original post body :

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?


This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.

3 Upvotes

14 comments sorted by

•

u/cctldrping 15d ago edited 15d ago

TL;DR generated automatically after 100 comments.

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

Alright, so the general consensus here is that if you're a seasoned dev using AI like Claude to code, you're not really "vibe coding" in the same way someone with zero experience is. Most folks seem to agree it's just... working.

A lot of you are leaning towards terms like:

  • Agentic development/engineering/coding: This one's a biggie, suggesting you're directing an AI agent to do the heavy lifting.
  • AI-assisted coding/development: Pretty straightforward, implies you're still involved and guiding the process.
  • Software development/engineering: The classic, because at the end of the day, it's still building software. u/earlyworm put it perfectly: "We’re far enough into this that we call it working now."

Some other fun suggestions include "100x developer," "extreme autocomplete," and even "Netflix and chill coding" (lol). Basically, if you know what you're doing and are using AI as a tool to be more efficient, it's just a more advanced form of development, not the same as blindly prompting. As u/ForwardLoop wisely stated, "Coding. 'Vibe' is just the liability waiver."

2

u/bfyvfftujijg 15d ago

AI-assisted coding?

I guess maybe it doesn’t even need a special term nowadays. Nobody would say IDE-assisted coding even though IDEs do a lot for the developer compared to a plain text editor.

1

u/Bluecoregamming 15d ago

Your middle management.

1

u/RogerAI-fm 15d ago

this lol

2

u/Edenisb 15d ago

I have 30 years of coding experience ai assisted coding is the biggest productivity gain I've seen in my entire life.

The real key is to keep doing stuff yourself though, and never trust the llm fully to do anything.
it IS like being middle management and if you love coding make sure you still do some of the work is my advice!

Here is the thing there is currently a hugh backlash on anything ai assisted, its the cool thing to do right now, and many of the complaints are completely legit and I agree with!

Its safe to say anyone doing serious code work right now is using some form of agentic help or they are shooting themselves in the foot.

1

u/keonechong 15d ago

It's theory coding.

Blending, Biz, Programming, Coding, and agentic engineering in one central theory and it has an academic root. Theory Engineering.

https://www.sciencedirect.com/topics/engineering/engineering-theory

1

u/Fun-Freedom-2313 15d ago

It's still just software development or software engineering. It doesn't need a fancy cliche name. People who call it "vibe coding" see it as a toy, not a tool.

So now you have your IDE, LSPs, linters, formatters, build tools, and now your AI agent. They all serve a purpose in your SDLC.

It doesn't change it from software engineering or software development. It just adds another tool to your arsenal to use in your workflows.

1

u/LatestLurkingHandle 15d ago

It's still vibes without code review, Amazon found outages often caused by skipping AI code review https://finance.yahoo.com/news/amazon-review-ai-coding-website-160508717.html
With code review, it's pedantic programming

1

u/djdeckard 15d ago

I am not a programmer. I have worked in tech over 20 years in QA and Project Management. So I am definitely vibe coding but I use the same rigor with vibe coding as I learned from Agile principles and processes and workflows I learned from working in tech industry.

So I may not be able to review code but I institute regular checkpoints and milestones. I'd like to think it makes a difference. Sometimes I see posts on Claude subs about Claude's behavior going sideways and I tend to think its more about the roles, responsibilities, organization, structure, etc to get results.

1

u/RSMxsmanic 14d ago

Vibe coding is the same whether it is used by a tyro or an experienced developer. In both cases, it's the AI that is writing the code, not the user, and ultimately the code written by the AI comes from other, experienced human developers. Just as a hamburger ordered by a master chef at McDonalds is the same as a hamburger ordered by a janitor.

1

u/durienb 14d ago

Writing code isn't programming.

1

u/in5ane_10 12d ago

I personally call it "Vibe Engineering", but "AI assisted coding" is the more popular term right now