What if English is not your first language and you are afraid of sounding silly when you email or text someone?
Don't paste the AI, please
41–50 of 632 posts
Re: Don't paste the AI, please
#42Re: Don't paste the AI, please
#43What if English is not your first language and you are afraid of sounding silly when you email or text someone?
Re: Don't paste the AI, please
#44I’m not convinced tbh, a lot of my colleagues messages are “x broken” or “I do y” … no context whatsoever, and then I have to coax their context for making these decisions. Since people started using Claude now I get full context of everything… might be too much sure, but to be honest over-communicating seems better than under-communicating - sure it’s boring and tedious but that shifts the blockage to me. Otherwise…
Context is everything.
Btw, Claude code sent my first accidental AI email yesterday. I guess permissions changed? Before it could only draft. Uhoh, waiting for the onslop.
Re: Don't paste the AI, please
#45yes, its all ai writing. A bunch of the metaphors here dont make sense. "read it all, yes even the bullets. especially the bullets" if you read one thing from a large wall of text, its gonna be the bullet points, right? thats a big part of what they're for? "It is the conversational equivalent of forwarding the email." this is a terrible metaphor. it seems to rely on the idea you would be mad if you sent an email to…
Re: Don't paste the AI, please
#46Re: Don't paste the AI, please
#47I’m not convinced tbh, a lot of my colleagues messages are “x broken” or “I do y” … no context whatsoever, and then I have to coax their context for making these decisions. Since people started using Claude now I get full context of everything… might be too much sure, but to be honest over-communicating seems better than under-communicating - sure it’s boring and tedious but that shifts the blockage to me. Otherwise…
And I think this is where one key argument on the page itself I think fails:
> The person on the other side has the same tools you do.
Yes, the person on the other side has Claude; but in many cases, their Claude doesn't have the same context as my Claude. Saying, "This thing happened in an area of the code I don't have any expertise in. Below is Claude's analysis, which I'm not qualified to assess" is I think a valid time to copy and paste LLM output. [1]
The other thing to say is that it can be a "LMGTFY" style response; i.e., "Why did you ask me that, when you could have gotten a perfectly good answer from ChatGPT?"
[1] In the particular case I'm thinking about, it was a bug in an ocaml component; I don't know ocaml or need to know it; handing Claude's analysis 'caveat emptor' to the maintianers who do know ocaml I think is more helpful than not.
Re: Don't paste the AI, please
#48Heh. Just got done writing (by hand!) a Principles of AI Use document for my (ironically) AI enablement firm, the first of which is: Write as yourself. You’re being paid for your expertise and insights. Communicate them directly to us. Copying and pasting Claude responses into Slack or an email directly shifts the burden of comprehension and understanding to everyone else, and worse, risks skipping that step for your…
Re: Don't paste the AI, please
#49Agree that it isn’t nice to just copy & paste, but the assumption that your AI generated answers will the same of someone’s else is wrong. Everyone using AI for a while built a different set of preferences, memories and context in general which influence the answers.