Live data from Hacker News

Don't paste the AI, please

dontpastetheai.com

101–110 of 632 posts

Re: Don't paste the AI, please

#101
The premise of the article is that everyone has access to the “same tools” but that’s glossing over the specialization inherent in a specific expert’s harness config (memories, skills, rules, repos, etc) that produce actually helpful responses (eg engineer’s view vs product manager’s view).

Re: Don't paste the AI, please

#102

Heh. 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…

Am I the only one suspicious of your comment?

> Write as yourself.

Unless it's your first day on HN (it's not 2008 account), most people use paragraphs and sentences longer than 2-5 words. Something like "You, directly." in the middle of all that has a certain vibe to it.

> Copying and pasting Claude responses... directly shifts the burden of comprehension

Most definitely.

The problem is we live in a world where people try to pass off copy pastes as their own all the time, many even smart enough to remove the em-dashes now. So I don't think that's going away soon. Your first sentence seems human, the rest doesn't match the tone at all.

Re: Don't paste the AI, please

#103
I remember back in the day when you could apply this to Google search results. When I was freelancing, I had a number of people I worked with who would fire off fast questions, but they would still pay me for my time. Then I would return what was essentially a Google search result shortly after. Yes, I would send my own answer, not some paste from Google.

But the point is. They had search, so why didn't they think to do the search? They had the same tools as I did. And yet regularly they couldn't think of the answer. I still deal with this with AI today. When you ask a question, maybe you're asking for the interpretation of the question by the person on the other side. And it's that interpretation that goes to the LLM. Or otherwise some filter of how that person thinks about the question differently than you do.

Re: Don't paste the AI, please

#104
Sorry this website is too polite.

DO NOT FUCKING PASTE AI RESPONSES TO ME, EVER, PERIOD.

When someone tells me they "talked to Claude" they sound retarded. Just tell me you looked into it, and I fucking swear to god if you just took what Claude said verbatim and do not understand the problem then you are a cunt and I will stop working with you.

When someone pastes LLM output in chat I completely ignore it. I will just continue the conversation as if they said nothing and silently mark them as cretinous in my mind.

This is not up for debate, you will talk to me in short well formed sentences and get to the fucking point or you will fuck off

Re: Don't paste the AI, please

#105

Heh. 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…

Thanks for sharing your thoughts. One of the best frameworks I have encountered, and one I point people to whenever I can, is the AI Fluency framework by Anthropic, Prof. Joseph Feller (University College Cork), and Prof. Rick Dakan (Ringling College):

https://www.anthropic.com/learn/claude-for-you

This framework provides a more abstract way of thinking when working with AI systems. Especially valuable to me is the pattern of the 4 D's: Delegation, Description, Discernment, and Diligence, which I have now internalized whenever I use AI systems. It helps me understand my own and others' (mis)use of AI systems a bit better.

Re: Don't paste the AI, please

#107

Heh. 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…

It's sad that there is a chance people put your guide into AI and ask it to "summarize"

They will paste it to their agent and ask it to live up to those requirements

Re: Don't paste the AI, please

#110
post #103

I remember back in the day when you could apply this to Google search results. When I was freelancing, I had a number of people I worked with who would fire off fast questions, but they would still pay me for my time. Then I would return what was essentially a Google search result shortly after. Yes, I would send my own answer, not some paste from Google. But the point is. They had search, so why didn't they think to…

Translating a client question to an actual technical question is the hard part I guess. Google-fu is still a thing, and absolutely a thing you were/are getting paid for it seems.
Post reply on HN