{"slug": "stop-using-claude-like-a-rubber-duck-real-code-review-strategies", "title": "Stop Using Claude Like a Rubber Duck: Real Code Review Strategies", "summary": "A developer shares strategies for effective AI-assisted code review, emphasizing specificity in prompts to get actionable feedback rather than generic comments. Techniques include asking about performance concerns, edge cases, and failure modes, as well as using diffs to highlight changes. The developer warns against having the same AI both write and review code, suggesting using a different tool or a human for serious reviews.", "body_md": "So you've started throwing your code at Claude or ChatGPT for reviews. Cool. But if you're copy-pasting your entire 200-line function and waiting for generic comments, you're wasting everyone's time—including the AI's.\n\nHere's what actually works.\n\nWhen you dump code and ask for feedback, you get feedback. Generic feedback. \"Good variable naming here\" and \"Consider extracting this logic\" and other things that read like they came from a linter output.\n\nThe AI doesn't know what you're worried about. Is the performance sketchy? Does the error handling suck? Are you confused about the logic? It's guessing.\n\n**Bad:** \"Review this code\"\n\n**Better:** \"I'm worried this function will timeout on large datasets. Walk me through the time complexity and suggest optimizations.\"\n\n**Bad:** \"Does this have any bugs?\"\n\n**Better:** \"I refactored our auth flow here. Are there edge cases around concurrent requests that would break this?\"\n\n**Bad:** \"Is this readable?\"\n\n**Better:** \"This logic is getting complex. Can you explain what each section does in plain English, and if any part is confusing, suggest how to rewrite it.\"\n\nSpecificity changes everything. The AI goes from guessing to actually helping.\n\nHere's my workflow:\n\nExample:\n\n```\nI changed the payment retry logic from exponential backoff to fixed intervals. \nCan you trace through what happens if a request fails 5 times in a row? \nAre there any issues with the new approach?\n```\n\nThe AI walks you through the logic. You spot problems. You learn something. This is how code review is supposed to work.\n\nInstead of pasting the new function, show the diff:\n\n```\nWe changed from:\n```\n\npython\n\nfor user in users:\n\nif user.premium:\n\nprocess(user)\n\n```\nTo:\n```\n\npython\n\npremium_users = [u for u in users if u.premium]\n\nfor user in premium_users:\n\nprocess(user)\n\n```\nQuestion: \"Does this change the memory profile? Any performance difference?\"\n```\n\nplaintext\n\nThe AI can see exactly what changed. Way easier to spot implications.\n\nThis is underrated. Instead of asking for bugs, ask for failure modes:\n\n```\nWe're using this to batch process 50,000 records at a time. \nWhat could break? What edge cases should we test?\n```\n\nplaintext\n\nThe AI will walk through timeout scenarios, memory issues, partial failures, etc. You now have a checklist.\n\nSometimes you just want confirmation. That's fine:\n\n```\nI think this recursive approach is correct, but I want a fresh pair of eyes.\nWalk through the base case and how it handles depth limits?\n```\n\nQuick, specific, useful.\n\nYou're the expert. The AI is a tool. Use judgment.\n\nThe actual benefit of AI code review isn't getting perfect feedback. It's **thinking through your own code while someone (or something) listens**. Explaining your logic out loud catches gaps. Having it reflected back helps you spot assumptions you didn't know you made.\n\nThat's worth the 30 seconds of prompting.\n\nIf Claude wrote the code and you're asking Claude to review it, you're in a loop. Works okay for minor tweaks, but for serious review, paste it to ChatGPT, Claude's competitor, or better yet, have a human look at it. Different perspectives catch different things.\n\n**Want more on building with AI sustainably?** Check out [LearnAI Weekly newsletter](https://learnairesource.com/newsletter) for practical patterns and tools that actually save time.", "url": "https://wpnews.pro/news/stop-using-claude-like-a-rubber-duck-real-code-review-strategies", "canonical_source": "https://dev.to/learnairesource/stop-using-claude-like-a-rubber-duck-real-code-review-strategies-58d8", "published_at": "2026-06-18 15:00:31+00:00", "updated_at": "2026-06-18 15:21:28.106436+00:00", "lang": "en", "topics": ["developer-tools", "artificial-intelligence", "large-language-models", "ai-tools"], "entities": ["Claude", "ChatGPT", "LearnAI Weekly"], "alternates": {"html": "https://wpnews.pro/news/stop-using-claude-like-a-rubber-duck-real-code-review-strategies", "markdown": "https://wpnews.pro/news/stop-using-claude-like-a-rubber-duck-real-code-review-strategies.md", "text": "https://wpnews.pro/news/stop-using-claude-like-a-rubber-duck-real-code-review-strategies.txt", "jsonld": "https://wpnews.pro/news/stop-using-claude-like-a-rubber-duck-real-code-review-strategies.jsonld"}}