{
  "video_id": "reddit_1vvo1a5",
  "channel_slug": "ClaudeAI",
  "channel_handle": "r/ClaudeAI",
  "title": "Devs who actually use Claude Code properly (not vibe coding) — what's your take?",
  "url": "https://www.reddit.com/r/ClaudeAI/comments/1vvo1a5/devs_who_actually_use_claude_code_properly_not/",
  "external_url": null,
  "upload_date": "20260822",
  "published_at": "2026-08-22T21:09:11+00:00",
  "transcript": "Every time AI coding tools come up you get the same three replies: \"it'll break in prod\", \"full of security holes etc..\",\"if AI codes better than you, you never really knew how to code\"\n\nFair enough sometimes, especially when people just prompt and pray with no review. But that's not what I'm doing, I think through architecture first, bake security constraints into the prompt, write tests for every feature, and manually test both backend and frontend before trusting anything. Basically treat it like a fast junior dev I still have to check.\n\nI also want to hear from people who can't code but use Claude Code seriously (write proper tests, ask for tradeoffs, don't just accept the first output) — did it hold up long term, or did stuff break later that you couldn't catch?\n\nWhat's the actual workflow you use to manage these tools correctly, and where does it still fail even when you're careful?\n\n\n\n--- Top Comments ---\n\n\n[1 upvotes] **TL;DR of the discussion generated automatically after 50 comments.**\n\n**The overwhelming consensus is that Claude Code is a massive productivity booster, but only if you stop \"vibe coding\" and treat it like a tool, not a magic wand.**\n\nThe most common analogy in the thread is that Claude is **a brilliant but naive junior developer.** It's incredibly fast and skilled at writing code, but it has zero business context, makes silly mistakes, and needs constant supervision. You are still the senior dev who is ultimately responsible for the code.\n\nHere's the workflow the pros in this thread are using:\n\n*   **Plan & Architect First:** You, the human, must think through the architecture and security constraints. Don't just ask Claude to \"build an app.\"\n*   **Test-Driven Development (TDD) is Your Friend:** Make Claude write tests for every feature *before* it writes the implementation. This is the best way to ensure the code does what you actually want.\n*   **Review Everything:** No one is blindly merging AI-generated code. A human review is non-negotiable to catch architectural flaws and subtle bugs.\n*   **Scope it Down:** Give the AI small, well-defined tasks with clear context. It stru\n\n[178 upvotes] It’s allowed me to catch up and surpass the speed the business thinks I can operate at.\n\nNow I can do tickets in peace and have some free time for all the fucking meetings \n\n[110 upvotes] It’s amazing as long as you drive it properly. Treat it like a junior extremely good at writing code but who doesn’t know anything about company internal rules and you’ll do amazingly well.",
  "transcript_chars": 2533,
  "ingested_at": "2026-08-23T01:30:04.570964+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 69,
    "upvote_ratio": 0.7,
    "num_comments": 82,
    "author": "Positive-Crazy-9974",
    "is_self": true
  }
}