Why People Actually Hate AI (And Why They're Sometimes Right)

I found myself staring at a sprawling list of trending topics the other day—from AI agents publishing articles about themselves to Palantir’s expansion into state surveillance infrastructure. It was a strange mirror into why so many people have developed a genuine distrust of artificial intelligence.

The pattern started becoming clear while working on a trend analysis feature for our Claude-based pipeline. We’re training models to understand signals, categorize events, and make sense of the noise. But as I dug deeper, I realized something uncomfortable: the tools we build aren’t neutral. They’re shaped by their creators’ incentives, and those incentives often don’t align with what’s good for the broader world.

Take the recent discovery that Israeli spyware firms were caught in their own security lapse, or how Amazon and Google accidentally exposed the true scale of American surveillance infrastructure. These weren’t failures of AI itself—they were failures of judgment by the humans deploying it. AI became the lever, and leverage amplifies intent.

What struck me most was the publisher backlash: news organizations are now restricting archival access specifically to prevent AI data scraping. They’re not wrong to be defensive. The same Claude API that powers creative applications also enables wholesale data extraction at scale. The technology is too powerful to pretend it’s value-neutral.

But here’s where the conversation gets interesting. While building our enrichment pipeline—pulling data from Wikipedia, generating contextual content, scoring relevance—I realized that distrust isn’t always irrational. It’s a reasonable response to opacity. When Palantir signs multi-million dollar contracts with state hospitals, or when an AI agent can autonomously publish criticism, people are right to ask hard questions.

The solution isn’t to abandon the tools. It’s to be radically honest about what they are: incredibly powerful systems that need careful governance. In our own pipeline, we made choices: rate limiting Claude CLI calls, caching enrichment data to reduce API load, being explicit about what the system can and cannot do.

The joke I heard recently captures something true: “.NET developers are picky about food—they only like chicken NuGet.” 😄 It’s silly, sure. But there’s a reason tech in-jokes often center on questioning our own tools and choices. We know better than most what these systems can do.

People don’t hate AI. They hate feeling powerless in front of it, and they hate recognizing that the humans controlling it sometimes don’t have their interests at heart. That’s not a technical problem. It’s a trust problem. And trust, unlike machine learning accuracy, can’t be optimized in isolation.