I'm going to be a bit contrarian here. In general, I 100% agree, just send me the prompt; however sometimes I feel an LLM can help structure thoughts. It can be a good sparring partner. If you proofread your LLM content, re-prompt until it sounds right and no longer like AI content, and feel that it actually conveys the information incredibly well, then I'm happy.
One of the instructions I've hammered into Claude is "Write like a human. I don't want this to sound like AI content. Your standard style of writing would fail miserably if it was reviewed by an English teacher. I want you to write prose that is nice to read. For example, write full sentences instead of bullet points."
It works wonders. Suddenly, my plan documents are something I actually understand, and something I'd be happy to share as an RFC. They still need iterating every time before they're ready to share, but I no longer have "the honest truth is" and other BS in my output. It's so refreshing for my brain to be able to actually focus on the content.
I've noticed this with my partner, too. She used Claude to draft a strategy document and felt completely overwhelmed. A classic moment of "AI did all the thinking for me, but now I don't know what I'm presenting". Once I helped her prompt Claude into writing the strategy in proper English, she understood what the AI was proposing, rejected large parts of it, iterated several times and ended up with a draft document where she edited the finishing touches herself and felt that it was truly hers. The AI was still incredibly useful: it helped her with the blank slate problem, and tremendously sped up her workflow.
So yeah, if you proofread and iterate on your AI's output until you feel you'd be proud if you had written it yourself, I'm happy to read it, too.
I'll be even more contrarian: I don't care if someone didn't write it as long as it's good (that's the major problem). I don't mind people using quotes when writing either. It's just that typically people (used to) curate their words before presenting them as writing. Although I'd prefer it if they also credited/explained what they used to write it in the case of heavy AI generation.
One of the instructions I've hammered into Claude is "Write like a human. I don't want this to sound like AI content. Your standard style of writing would fail miserably if it was reviewed by an English teacher. I want you to write prose that is nice to read. For example, write full sentences instead of bullet points."
It works wonders. Suddenly, my plan documents are something I actually understand, and something I'd be happy to share as an RFC. They still need iterating every time before they're ready to share, but I no longer have "the honest truth is" and other BS in my output. It's so refreshing for my brain to be able to actually focus on the content.
I've noticed this with my partner, too. She used Claude to draft a strategy document and felt completely overwhelmed. A classic moment of "AI did all the thinking for me, but now I don't know what I'm presenting". Once I helped her prompt Claude into writing the strategy in proper English, she understood what the AI was proposing, rejected large parts of it, iterated several times and ended up with a draft document where she edited the finishing touches herself and felt that it was truly hers. The AI was still incredibly useful: it helped her with the blank slate problem, and tremendously sped up her workflow.
So yeah, if you proofread and iterate on your AI's output until you feel you'd be proud if you had written it yourself, I'm happy to read it, too.