Don't Just Paste the AI — Write Your Own Take

The site dontquotetheai.com makes one point bluntly: pasting raw AI output into a reply is lazy and unhelpful. If someone asked you a question, they want your take — not a generic answer they could've fetched themselves in four seconds.
What's the Problem?
Someone asks a real question. You pop it into a chatbot, copy the answer, and send it back. It feels fast and helpful. But the recipient has the same tools you do. If they wanted the generic answer, they'd have gotten it themselves. They asked you because they wanted your context, taste, and judgment.
What to Do Instead
- Use the AI as a drafting partner. Read what it generates, then write your own take.
- Extract only the bit that actually answers the question. Drop the rest. Three sentences from you is plenty.
- If a piece of the AI's answer is genuinely useful, quote it and say why. For example: "I checked with Claude and this part lines up: ..."
- If you have nothing to add, say so. "No strong opinion here" is a real, helpful reply.
Sending This to Someone
If a colleague drops a wall of model output in your DMs, Slack, or PR review, you can send them dontquotetheai.com. No lecture required. There's also an 'angry version' for stronger feelings (not safe for sending to your manager).
The site is a spiritual cousin of nohello.net and dontasktoask.com. Written by a human, on purpose. Free to share, remix, and translate — PRs welcome on GitHub.
📖 Read the full source: HN AI Agents
👀 See Also

Practical Strategies to Avoid Claude Rate Limits on $200 Max Plan
A developer shares specific techniques that have prevented throttling on Claude's $200 max plan for over a month, including SQLite database queries, context handoff systems, and strategic hardware deployment.

Claude Code Plugin Bug Causes Skills to Load Twice, Increasing Context Compaction
A bug in Claude Code causes plugins to load every skill twice due to stale cache directories and symlink duplication, significantly increasing system prompt size and triggering frequent context compaction. The source provides check scripts to identify the issue and fix scripts to remove stale plugin versions and duplicate symlinks.

How to Stop Hitting Claude Limits: Treat Each Session Like a Token Budget
User shares how they fixed daily Claude limits by stopping message bloat — scope the task, load only relevant context, clear after each session. Includes practical workflow & infographic.

Claude Code Works Better as Code Reviewer Than Generator
A developer shares that Claude Code produces more grounded output when used to review existing code rather than generate from scratch. Key practices include starting sessions with current implementations, maintaining project context files, and restarting sessions when responses degrade.