upvote
There's a difference between using Claude and sharing its unfiltered output.
reply
I’ve never shared Claude text output with another human without explicitly flagging it as such. I believe my ability to communicate effectively in my own words is a large part of the value I offer and Claude’s writing (at least in relation to code) is so convoluted and malformed that I wouldn’t dream of attempting to pass it off as my own.

It has a utility in the same way that raw ingredients have a utility in a kitchen. The chef doesn’t just drop a messy pile of uncooked meat and vegetables onto your plate and tell you to figure it out. That’s exactly what people are doing when they vomit out a bunch of impenetrable slop and expect the reader to do the hard work of comprehending it on their behalf.

You can’t expect others to care about what you’re saying if you’ve not spent a moment considering how best to say it. The reader’s time is no less valuable than your own. If you think composing a readme for your project is worth zero minutes of your time, that’s the appropriate amount of time for readers to allocate to it.

For whatever it’s worth, I also cancelled my Claude subscription recently and shifted back to OpenAI solely because I find its outputs far more readable. I’ll even accept a slight hit on model performance as a trade-off. If I’m unwilling to read Claude-speak when I’m being paid an hourly rate, you can be sure I’m not reading it for free.

reply
> I’ve never shared Claude text output with another human without explicitly flagging it as such.

You've likely shared code written by OpenAI and don't mind subjecting other to it. So why should technical docs be different?

I think you're fighting a losing fight trying to get people to waste their time hand-writing tech docs just to avoid triggering over-sensitive Claude power users because they saw the word "gate".

reply
code is used to 'speak' to computers. prose is meant for human communication.

if your readme is meant to only ever be read by 'agents' then fine. if you want actual humans to read it, write in a human language, not LLM-speak.

it literally could not be more simple.

reply
Code and prose are different things, but that aside, no, I don’t expect anyone I work with to be subject to my mindless one-shotted PRs – which is as close a comparison I can think of on the development side. I also wouldn’t consider a readme to be a pure technical doc. It’s very likely to be the first, and possibly last, impression someone forms of your project. It matters.

I’m not fighting any particular fight, I’m just saying that the lack of care stands out to me, and evidently to others, and that anyone releasing a new project might want to consider whether they want it to be perceived in that way.

reply
> I’m just saying that the lack of care stands out to me

You don't know how much they cared. You also don't know if they reviewed the README before publishing, or if was a mindless one-shotted PR that nobody looked at. The word "gate" isn't a smoking gun here, other than to prove that the reader uses AI a ton and is ironically now triggered by it. If your criticism was more substantial: targeting the content rather than the use of a trigger word, then I might agree. But you haven't done anything but project your own bias.

reply
“Gate” was just the trigger to quickly scan the rest of the copy, at which point AI’s fingerprints are so obvious that it’s impossible to believe a human wrote it. I haven’t bothered to check, but I’m sure any of the AI detector sites would light up like a Christmas tree on this.
reply
These criticisms are empty, though. Just because it's AI-generated doesn't make it bad. You're not saying what's bad about it other than "I can tell AI wrote it, therefore I reject it". Which imo is wildly hypocritical considering you power use the exact same AI tools to auto-generate output.
reply
it's full of AI Slop fingerprints. Clearly hasn't been read or edited by a human before being published, or they're already deep in the brain rot that they can't see just how bad it is.
reply
What they're saying is that if something is not worth the time needed to write it, it's not worth the time needed to read it either.
reply
Great, as long as they never share any of their Claude output (to include code) with anyone.

But even better: if Claude's output is so torturous, they should probably just stop using it altogether rather than thumbing their nose at other people that use it.

reply