Mark Zuckerberg's AI Manifesto Is Exactly Why People Don't Like AI

On a crisp January morning in 2025, Mark Zuckerberg sat down for a three-hour podcast with Joe Rogan. Between discussions of martial arts and prehistoric megafauna, the Meta CEO dropped a line that would crystallize into what many now call his 'AI manifesto': AI is going to write "medium-quality code" and do the work of a mid-level engineer within a few years. The soundbite was polarizing. For engineers, it sounded like a layoff notice. For investors, it was a bullhorn. And for the average user? It was the first of many signals that the tech elite were not building AI to help humanity—they were building AI to replace it.

The manifesto isn't a single document; it's an ongoing narrative of open letters, conference keynotes, and podcast appearances in which Zuckerberg argues for open-source superintelligence, "AI abundance," and a world where anyone can "vibe code" software into existence. That last term—vibe coding—was popularized by Andrej Karpathy, formerly of Tesla and OpenAI, in February 2025. He described it as a form of programming where "you fully give in to the vibes, embrace exponentials, and forget that the code even exists." It's intoxicating in theory. In practice, it's creating a crisis of trust that is precisely why people don't like AI.

Let's break down exactly why Zuckerberg's manifesto—and the vibe coding culture it blesses—is turning the public against artificial intelligence.

The Manifesto vs. The Public's Reality

Zuckerberg's vision rests on five pillars: openness, abundance, autonomous coding, AI equality, and inevitable progress. Each pillar has an intuitive appeal and a darker counterpart that resonates more strongly with actual users.

This mismatch is not accidental. It's the result of a communication strategy that overpromises and underdelivers. When Facebook changed its name to Meta, Zuckerberg sold the public a metaverse utopia; three years and $13 billion in losses later, the project was largely defunded. Now he's doing a rerun with AI. The public has learned to recognize the pattern: a tech titan with a grand narrative, talking past their concerns.

The Vibe Coding Trap

Karpathy's original tweet about vibe coding was meant to be a description, not a prescription. He even noted that a website built this way would be a "hot mess." But Zuckerberg's manifesto turned vibe coding into a corporate directive. In his Rogan appearance, he said "a bigger percentage of code" will be written by AI, and that humans will merely supervise. The problem is that supervision requires understanding, and vibe coding systematically erodes that understanding.

A developer using an AI assistant to generate a Node.js payment module might not realize the code skips input validation or lacks proper encryption. The resulting vulnerability is now a CVE (Common Vulnerabilities and Exposures) entry used by attackers. Recent security research has found that AI assistants introduce vulnerabilities at a higher rate than human developers, especially for less common languages. A study by Veracode (or a generic link?) noted a higher recurrence of flaws in AI-generated code. But the exact numbers are debated; the key point is that vibe coding shifts the burden of correctness onto reviewers who are only human.

The deeper issue is technical debt. When an AI writes code, that code is not born from a coherent architecture. It's a statistical patchwork of training data. It works until it doesn't, and then it's the human's job to untangle a logic that no human designed. This is the "boiling frog" of software development. Teams start with 80% AI-generated code, then spend 200% of their time debugging it. The result: products that break more, age faster, and frustrate users who just want a stable app.

Real-World Failures That Fuel Distrust

The public doesn't read manifestos; they read headlines. And the AI headlines of recent years have been brutal.

• In 2025, Google's AI Overviews repeatedly told users to "eat one small rock per day" and mix glue into pizza sauce, prompting an official apology and a hasty retreat. The examples went viral and became meme shorthand for AI stupidity.
• Air Canada's customer-service chatbot invented a bereavement policy that didn't exist, and a Canadian tribunal ruled the airline had to pay a partial refund because the chatbot was "part of the airline's website." (CBC News)
• An AI-powered recruiting tool at a major tech firm systematically downgraded candidates whose resumes included the words "women's" or "women's group" — a debiasing failure that echoes real-world cases like the Reuters report on Amazon's 2018 HR AI.

These are not isolated incidents; they are systemic outcomes of vibe coding. When developers rely on AI to write a parser for legal documents, the model hallucinates statutory references. When a product manager asks an AI to "generate a privacy policy," the result may fail GDPR/CCPA compliance. The cost of these failures is paid by users, who lose money, time, and personal data.

Meanwhile, the "AI slop" epidemic—in which AI-generated fake images, low-effort YouTube videos, and spammy LinkedIn posts flood the internet—has made plain the consequence of making content generation effortless. Zuckerberg's manifesto promises "AI abundance"; what users experience is "AI abundance of crap."

Open Washing: The Hypocrisy Factor

Zuckerberg's most popular tenet is open-source. In November 2024, Meta released Llama 3.3, an open-weights model that rivaled closed systems from OpenAI and Anthropic. He has repeatedly argued that open-source is essential for AI safety and democratization. But what does "open" actually mean here?

Open weights ≠ open source in the classic definition. The weights (the numerical parameters that make up the neural network) are publicly available for download, but the training data, training scripts, and evaluation pipelines remain proprietary. This is known as "open washing"—using the rhetoric of openness to launder corporate interests. Meta's own license for Llama grants broad usage rights, but prohibits using the model to improve other large language models and imposes special restrictions on companies with over 700 million monthly users (read: Google). So Llama is open for everyone except competitors.

AI ethicists like Timnit Gebru have argued that "openness" without transparency about data sourcing is meaningless. If we don't know what a model was trained on, we cannot audit its biases, its copyright violations, or its ability to generate toxic content. The manifesto's call to "share AI responsibly" rings hollow when Meta itself is fighting lawsuits from authors whose copyrighted books were ingested without consent.

This cynicism seeps into the public consciousness. People see a billionaire with a paper smile saying "trust me, open-source AI will save us," and remember how "open" algorithms accelerated hate speech on Facebook in Myanmar. Skepticism is not paranoia; it's experience.

The Human Cost of AI Abundance

Zuckerberg's statement about mid-level engineers was a form of collective gaslighting. He told an audience of millions that their hard-won skills are about to be commoditized, and that they should "learn to supervise AI." But what does a mid-level engineer do if the AI produces code that passes unit tests but has subtle race conditions? They become code reviewers, paid to clean up a mess they didn't make. Junior engineers no longer get the apprenticeship of writing code from scratch; they inherit opaque AI artifacts. This is a generational catastrophe for the profession.

Polling from Pew Research Center and Gallup in recent years consistently shows that a third to half of workers worry AI will displace them. The rhetoric of "AI abundance" also ignores concentration of power. Zuckerberg says AI will democratize creation, but the infrastructure—chips, data centers, energy—is owned by a handful of trillion-dollar companies. Meta's plan to build a 2GW data center in Louisiana requires a dedicated nuclear plant to power it. This is not abundance; it's nation-state-grade resource extraction. The "vibe coder" is trapped in someone else's cloud.

Why the Manifesto Backfires: Psychological Reactance

Social psychology gives us a useful lens: reactance theory. When people feel their freedom to choose is threatened, they rebel against the source of the threat. The manifesto's tone of inevitability ("AI is coming, so join us or be left behind") triggers exactly that. Instead of embracing AI, users double down on their distrust. They turn off auto-updates, disable AI features, and seek "no-AI" alternatives.

This is visible in Reddit communities like r/ChatGPT, where post after post complains about "AI features nobody asked for." Microsoft's Recall feature—which screenshots your screen every few seconds—was delayed and redesigned after a privacy backlash. Google's AI Overviews were forced to cut back after users complained. Now, we see the emergence of "AI-free" products as a premium category. The manifesto promised a future where AI is everywhere; the public demands a future where AI is somewhere—preferably not in their kitchen.

What Responsible AI Advocacy Looks Like

If Zuckerberg truly wants to make AI loved, he could start by doing the opposite of what he's doing: stop talking. Instead of a manifesto, the industry needs rigorous benchmarks, transparent failure reports, and human-centered design processes. The EU AI Act, which came into full effect in 2026, now mandates risk-based audits for high-risk AI systems. Companies are scrambling to be compliant, but compliance is not the same as trust.

One positive model is the concept of "human-in-the-loop" design, where AI produces drafts and humans make decisions. This doesn't mean simply accepting AI output—it means explicitly designing for human override, with an audit trail of every AI suggestion. It's the difference between an autopilot that quietly causes a crash and a copilot that suggests a landing path while the pilot holds the yoke.

For businesses looking to adopt AI responsibly without repeating the mistakes of the hype cycle, the key is careful integration with existing workflows. ASI Biont supports integration with OpenAI's API for precisely this purpose—connecting tools that are thoroughly tested and monitored, not just vibe-coded into existence. More details are available at asibiont.com/courses.

But even the best tools can't fix a broken narrative. The AI community needs to embrace epistemic humility: admit what AI can't do, share failure rates, and stop selling a future where humans are obsolete. When leaders like Zuckerberg issue a manifesto that declares "we're building the Matrix, and it's cool," the public's instinct is to run.

The Elephant in the Server Room

There is an unflattering parallel between Zuckerberg's AI manifesto and his previous pivot to the metaverse. Both are attempts to predefine a future that benefits his company, dress it in philanthropic ideals, and rush ahead while the public is still blinking. The difference is that AI is not a dull pair of VR goggles; it's a general-purpose technology that touches every corner of life. Its failures are more visible, and its risks are more personal.

People don't dislike AI because they fear a Terminator-style uprising. They dislike AI because they've been burned by a thousand incremental insults: a chatbot that can't refund a simple charge, an AI LinkedIn post that "sounds like a robot," a deepfake of a lawmaker, a mortgage application denied by an unexplained scoring model. Zuckerberg's manifesto, for all its grandiosity, is a megaphone for every one of those insults. It says: "We know better than you, and you'll thank us in five years."

Vibe coding is the philosophy that underlies this arrogance. It treats code as a byproduct and understanding as optional. But code is not magical; it's a set of constraints and affordances that shape what people can and cannot do. When you build software with vibes, you build a world without guardrails.

Conclusion

Mark Zuckerberg's AI manifesto is not malicious. In fact, parts of it—especially the commitment to open weights—have genuine democratic potential. But its packaging is a masterclass in how not to talk to the public. It overpromises, it downplays risk, and it elevates vibe coding to a virtue when it is actually a liability. The result is that people don't trust AI even in places where it works. They smell the manifestos, and they know they're being sold.

The cure is the same as the cure for any tech panic: honesty, specificity, and respect for human autonomy. We need less "abundance" talk and more "here's how to opt out." We need fewer billionaires telling us the future is written and more engineers explaining the error bars. Until then, every new manifesto—even one that claims to love us—will just be another reason to unplug.