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

Helpful Tips from the OpenClaw Community: A Deep Dive into AI Agent Optimization
Discover valuable tips from the OpenClaw community on optimizing AI coding agents for better performance and efficiency. These insights could revolutionize your AI projects.

OpenClaw v2026.3.13 adds per-agent cacheRetention config for OpenAI token cost savings
OpenClaw v2026.3.13 adds per-agent cacheRetention configuration that enables OpenAI's 24-hour prompt cache retention, potentially cutting input token costs by up to 90% for agents with heartbeat cycles longer than 10 minutes.

Fixing AI Agent Dumbness: A Shared Context Tree per Repo
The reason AI employees feel dumb isn't the model—it's lack of shared context. One developer's fix: a context tree repo with hierarchical markdown nodes, auto-maintained by the agent.

Eight Prompting Techniques That Improve Claude Output Quality
A Reddit user shares eight specific prompting techniques that consistently improved their Claude output quality, including commands like "Think through every layer before answering" and "Find the 20% of actions that drive 80% of results."