Social network Bluesky saw some intermittent service disruptions on Monday. On its own, this fact isn’t that noteworthy—Bluesky has seen similar service disruptions in the past, and this one coincided with widespread service problems being reported with other popular sites (Bluesky officially blamed the temporary problems on an “upstream service provider”).
What made this outage notable for many Bluesky users, though, was the instant assumption that it was the result of sloppy, AI-assisted “vibe coding” by the Bluesky development team.
Amid Monday’s service issues, many Bluesky feeds were filled with hundreds of posts that laid the blame on developers who were allegedly relying on unreliable AI tools to ship faulty code. Some used memes, others used alt text, still others used irony or wry humor to call out Bluesky’s development team for this alleged sloppiness.
Overall, though, the mood among these vibe-code blamers was one of righteous anger. “Any developer or programmer using ‘vibe-coding’ or any reliance on AI to code things is clearly too stupid to know how to do the job they’re paid to do and should be fired out of a cannon,” Bluesky user T-Kay wrote, summing up the, er, vibe. “Coding takes skill, not slop.”
bluesky employees: we are vibe coding the entire website using only AI now
yeah dude, i can tell
— lex luddy (ichiban appreciator) (@lexluddy.xyz) April 6, 2026 at 10:29 AM
It’s the kind of reaction that highlights just how many tech users are still reflexively repulsed by the idea that AI tools were used in any way to create the products they use. Even as professional coders are becoming increasingly enthusiastic about the power of AI coding tools, many end users still see them as a boogeyman to instantly blame for any and all observed ills in the tech industry.
“Things are changing. Fast.”
Before yesterday’s outage, many on the Bluesky development team faced social media backlash for admitting they used AI tools in their work. Bluesky founder and Chief Innovation Officer Jay Graber posted point-blank in late March that “Bluesky is made with AI, the engineers and even some non-engineers use Claude Code,” for instance. And Bluesky Technical Advisor Jeromy Johnson (who goes by the handle “Why” on the site) has been an outspoken proponent of AI coding tools, saying in February that “In the past two months Claude has written about 99% of my code. Things are changing. Fast.”
Bluesky CTO Paul Frazee later joined in with a (perhaps joking) reply to Johnson saying, “I vibecode at least as much.” Later, Frazee said that he saw a “call to action… for all of us to start utilizing this [AI] tech in our work.”
Public worries about AI tools “infecting” the Bluesky experience increased on March 28 when the company announced Attie, a side project that lets users build their own custom Bluesky feed by talking to a chatbot built on Claude Code. Bluesky team members said the tool’s eventual goal, as reported by TechCrunch, was to let users vibe-code their own social apps.
Until December of last year I was using LLMs as fancy autocomplete for coding. It was nice for scaffolding out boilerplate, or giving me a gut check on some things, or banging out some boring routine stuff.
In the past two months Claude has written about 99% of my code. Things are changing. Fast
While Attie is a separate product that is not part of the core Bluesky app, many AI skeptics in the Bluesky user base were still disgusted by what they saw as a worrying developer distraction at best and an unwelcome AI integration at worst. That was especially true given that Bluesky attracted many users from Elon Musk’s Grok-ified X with a 2024 promise not to use Bluesky posts to train any AI models.
“We hear the concerns about AI,” Graber posted last week in response to the uproar around Attie. “Our goal is to use this technology to give people greater control, not to generate content. Attie uses AI to help you create custom feeds without having to know how to code.”
These worries over AI coding and side projects had been marinating among the most anti-AI segments of the Bluesky user base for weeks before yesterday’s service disruptions. Given that setup, many seemed eager to jump to the conclusion that Bluesky’s issues must be connected to AI use among its coders, relishing the presumption with a clear sense of “this is what you get” schadenfreude.
This isn’t the only recent example of “vibe coding” being blamed for a tech snafu. When Anthropic accidentally leaked its client source code last week, some social media users similarly assumed it was the result of a sloppy vibe coder making a mistake while using Claude Code to push the release. While Anthropic’s Boris Cherny blamed the leak on human error during the code’s manual deploy process, that hasn’t stopped some from trying to tie the blunder to Cherny’s admission that the team relies on Claude Code to create “pretty much 100% of our code.”
Is it “vibe coding” or mere “AI-assistance”?
Potential leaks aside, the last year has given plenty of ammo to tech watchers predisposed to skepticism toward vibe coding. Sloppy AI coding assistance was blamed for a recent six-hour outage at Amazon, and in multiple recent stories of rogue coding agents irretrievably deleting files against human coders’ wishes. Then there are the well-founded worries about the security risks of vibe-coded software, and the many examples of vibe-coded projects that are unbearably buggy or unreliable.
But glitchy software and Internet service problems existed long before vibe coding was a thing, of course. Instantly attributing any software or service glitch you see to the scourge of AI-generated code, without evidence, is as presumptuous as assuming that AI demonstrates perfect reasoning.
On a personal level, I’ve been a software engineer since I was 12. I joke about the quality of my code, but the reality is that I take it incredibly seriously. The source of those jokes is humility to how difficult it is to write complex software and avoid bugs, or outages.
— Paul Frazee (@pfrazee.com) March 5, 2026 at 4:58 PM
Putting all code made with AI assistance into the same mental “vibe-coded slop” bucket can also obscure some important distinctions in how these tools are used. The original definition of “vibe coding,” as it was coined over a year ago, described amateurs and non-coders using AI to generate minimally working but extremely brittle code without understanding how it works. That’s completely different from experienced developers using AI-powered coding tools to program more efficiently while still using their accumulated coding knowledge to organize, check, and verify the code. As we wrote in a January hands-on deep dive into the bowels of AI coding tools, “even with the best AI coding agents available today, humans remain essential to the software development process.”
Frazee tried to highlight this distinction in an early March thread, clarifying how Bluesky developers use AI behind the scenes. “The Bluesky team maintains the same review, red-teaming, and QA processes that we always have,” Frazee wrote. “AI coding tools have been proving useful, but haven’t changed the fundamental practices of good engineering. Human review and direction remain key.”
That distinction has seemed to resonate with some Bluesky users, who have urged restraint for those eager to blame every service glitch on AI code. “There’s an actual conversation to be had about AI-assisted coding and being a software developer that architects more complex systems, and where AI can be incredibly useful,” Bluesky user Randi Lee Harper wrote. “But it’s impossible to have that conversation when folks not in tech jump in saying ‘AI is bad, always.’”
But even some who understand that Bluesky hasn’t suddenly been converted into 100 percent vibe-coded slop were happy for an opportunity to mock developers for using AI tools in the first place. “Is blaming vibe coding for the Bluesky outage plainly wrong? Yes,” Bluesky user Lucyfer wrote. “Is it funny? Also yes.”
In other words, even if vibe coding is merely a public boogeyman for many software glitches, it’s one that coders may have to get used to hearing about if they admit to using AI tools at all. “The lesson from today’s downtime isn’t that it was caused by vibe coding…” Bluesky user Dalton Deschain wrote. “It’s that if you use AI you will no longer get the benefit of the doubt and everyone will mock you for laziness regardless of the cause.”
