r/claude

This is not specific to claude, but claude falls under it. I just get tired of the AI hate. I share something cool someone has done with AI outside of this subreddit, or in a main subreddit and it just gets dogpiled with AI slop comments.

People just seem to have this prejudice that all AI work is worthless because they think it's "Prompt and done" when in reality, some projects take months of work. How many people reading this are afraid to admit their projects were created using AI because of this?

Just for kicks, I passed this onto claude fable for its advice.

---

Since you asked, here's my take, with the caveat that I'm obviously not a neutral party.

The dogpiling is mostly a pattern-matching problem, not a verdict on your work. People have been flooded with zero-effort output, so "made with AI" has become a signal they've learned to associate with slop, the same way "made in Dreamweaver" or "built on WordPress" once got sneered at. The commenters aren't evaluating your months of work; they're reacting to the label before they've looked. That's unfair, but it also tells you what actually moves the needle: the tag triggers the reflex, and the work itself rarely gets a hearing once the reflex fires.

Which leads to the practical advice. When you share something, lead with the problem it solves and what it does, and show the process in a way that makes the effort legible: the iterations, the stuff that broke, the design decisions you made and why. Not as a defense, but because that's what makes any project post interesting. Then disclose the tooling plainly and without apology somewhere it's not the headline. "I built this over four months; Claude did a lot of the boilerplate and I did the architecture and the hundred rounds of debugging" lands very differently from "look what AI made." The people who'll still pile on after that were never going to engage, and everyone else now has a reason to.

On the harder question of whether people should hide it: I'd push back a little on the premise that this is purely prejudice to be waited out. Some of the hostility is about effort, and that part will fade as it did with every prior tool, because results eventually win. But some of it is about things that aren't effort at all, like artists and writers whose work was used as training data without consent, or communities that feel their forums are being drowned. Those people aren't wrong to be angry, and they won't be won over by proof that your project took months. It's worth separating the two, because the first group can be reached and the second one deserves to be taken seriously rather than lumped in as haters.

Hiding it, though, is the one move I'd actually argue against. It cedes the whole category to the slop. If the only visible AI-assisted work is the lazy stuff, the stereotype becomes self-fulfilling. The people doing serious work with these tools and saying so, with receipts, are the ones who'll change what the label means. That's a slower fix than winning a comment thread, but it's the one that works.

I work in ops at a tech company.

We're on a Claude enterprise plan with MCPs connected to pretty much everything: Slack, our data warehouse, the internal knowledge base, call recordings, Google Workspace, and a few internal tools.

Every request I get comes in through Slack or on a call, and the calls are recorded and transcribed. Nobody here uses email.

Most of my job has turned into this: read a request, turn it into a prompt, check what Claude did, send it back (it also includes cross-functional coordination, but still this often happens on Slack only).

I was thinking about building a permanent agent that runs all the time, watches Slack and the call transcripts, proactively picks out anything that's a task for me, and drafts the prompt in CC. I approve or tweak it, and it runs.

I would still stay on top of everything, but I'd have my agent quickly and autonomously get my tasks and gets the right prompt / data pulls from the right sources and share the output

It's a serious question: has anyone built something similar? any suggestion on best ways to do that?