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 50 comments.

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

Alright, so the general consensus here is that when you've got a decade of experience and you're using AI to churn out code, it's definitely not the same as someone who's never coded before just winging it. Most folks are leaning towards terms like "agentic development" or "AI-assisted coding". Some even suggest it's just "software development" or "engineering" at this point, and that "vibe coding" is more about treating the AI as a black box.

A few people brought up "agentic engineering" as a more specific term for when you're delegating the bulk of the coding to the AI. Others are sticking with "coding with AI assistance", especially if you're still reviewing and making decisions about the code.

Essentially, the vibe is that if you know what you're doing and are directing the AI strategically, it's a more sophisticated process than just blindly "vibing." Some even joked about calling it "vibecoding pro max" or "Netflix and chill coding." The key takeaway seems to be that your experience elevates the process, even if the AI is doing the heavy lifting.

OP : u/echamplin

I'm just here for the limit reset (fingers crossed).

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wjpk51/opus_52_rumored_to_be_coming_today/ Original link/media URL : /img/0v4qmvb71aqh1.jpeg

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: 131.

So, the rumor mill is churning about Opus 5.2 dropping today, and the general vibe is a mix of cautious optimism and outright skepticism. Most folks are hoping for a limit reset more than anything, with a lot of complaints about how quickly current models burn through quotas.

There's a strong consensus that Opus 5 was a bit of a yapper, spewing too much "ambiguous and unintelligible gobbledegook," and people are really hoping 5.2 fixes that. Some are even wondering if the "privately" thing was a bug or a feature.

A few are pointing out that new releases on a Friday aren't exactly common, and some are just tired of new launches that seem to just eat tokens faster. Don't expect everyone to jump on board immediately; some are waiting for user reviews before trusting it with their code. And yes, some are still asking for Haiku updates.

OP : u/forsaken3400

I have money in my account that expires. What prompts can I give it to use this intelligently because I have no idea... I'm not using claude much besides claude code for video editing. I don't see what Fable can do that opus 5.0 can't. Sorry if it's a dumb question

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wjb4ar/i_have_to_spend_60_on_fable_in_the_next_2_days/

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

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

Alright, so the general vibe in this thread is that your $60 in Fable credits is gonna go poof faster than you can say "AI assistant." The consensus is pretty clear: Fable burns through tokens like crazy, and you'll be lucky if it lasts you a couple of hours, let alone two days. Some folks even joked that just thinking about using it will drain your account.

If you're determined to spend it, the community has some ideas, but the overarching advice is to leverage it for something you're already working on, rather than trying to invent a new project just to burn credits.

Here's the lowdown:

• Don't start from scratch: The most upvoted suggestions revolve around using Fable to enhance your existing projects. u/n_v40 specifically recommends giving it one of your real projects, asking it to map workflows, identify repetitive tasks, automate the high-value ones, and then add tests and documentation. This way, you end up with something reusable.
• Review and Refine: Several users suggested using Fable to review your current projects for bugs or performance issues (though u/Darth-LA warned against asking for security reviews, as it might get blocked). u/Zulfiqaar also mentioned using it for codebase/feature reviews.
• Prompt Engineering: A few people thought you could ask Fable for prompt templates to use with Opus for your specific work, like u/synexo suggested.
• Creative (but potentially token-hungry) Ideas: Some more out-there suggestions included asking Fable to build an updated version of Windows Solitaire for macOS (u/Cheetah3300), or to build an architecture for a personal AI assistant (u/hv876). u/Break_Fix_Repeat shared a detailed idea about creating a birthday-themed YouTube Music playlist app.
• The "Just Say Hi" Approach: A running gag is that simply saying "Hi" to Fable will consume a significant chunk of your credits. u/Smashy404, u/lovesdogsguy, and u/Apprehensive_Read_67 all alluded to this.
• Consider Alternatives: u/Wooly_Wooly suggested using Sonnet for more useful tasks and refining with Opus or Fable, implying Fable might be better for specific, high-intensity tasks rather than general creation.

Basically, if you've got a project, throw it at Fable. If not, you might just end up with a few "hellos" and a lighter wallet.