On Monday, Bluesky, the emerging social network, experienced some intermittent service disruptions. While service outages are not uncommon for Bluesky, this particular incident coincided with widespread issues reported by other popular platforms. The company attributed the temporary disruptions to an "upstream service provider," a standard explanation in the tech world.
However, what made this outage particularly noteworthy was the rapid shift in user sentiment towards the development team. Many Bluesky users quickly assumed that the problems stemmed from what they termed "vibe coding"—a practice where developers allegedly rely on AI tools for coding, leading to sloppy or unreliable code.
As the service issues unfolded, Bluesky feeds filled with an array of posts blaming the developers for leaning too heavily on these AI tools. Users employed memes, irony, and humor to mock the situation, expressing a collective frustration. One user, T-Kay, encapsulated the mood by stating, "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. Coding takes skill, not slop." This sentiment resonated with many who viewed AI-assisted coding with skepticism.
Skepticism towards AI tools seems to be a common theme among tech users, as many still harbor a strong aversion to the notion that AI could be involved in creating products they use daily. Despite the growing acceptance of AI tools among professional coders, end users often see them as scapegoats for any issues that arise.
Growing Concerns Over AI Integration
Before the outage, Bluesky developers had already faced backlash for openly admitting their use of AI tools. Jay Graber, Bluesky's founder and Chief Innovation Officer, stated in late March that "Bluesky is made with AI, the engineers and even some non-engineers use Claude Code.” Additionally, Jeromy Johnson, a Bluesky Technical Advisor, noted that AI tools had significantly contributed to his coding efforts, claiming that "in the past two months, Claude has written about 99% of my code. Things are changing. Fast.”
In response to the concerns regarding AI integration, Bluesky CTO Paul Frazee joined the conversation with a light-hearted remark, indicating his own use of AI tools. He further emphasized that there is a call to action for developers to harness AI technology in their work.
The public's apprehension about AI's role in Bluesky intensified with the announcement of Attie, a new feature allowing users to build customized feeds through a chatbot powered by Claude Code. While this tool is separate from the main Bluesky app, critics viewed it as an unwelcome attempt to integrate AI into the user experience, especially considering the platform's initial promise not to use user data to train AI models.
Graber addressed the uproar, stating, "We hear the concerns about AI. 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.”
Vibe Coding: A Boogeyman for Tech Glitches?
The backlash against "vibe coding" isn't isolated to Bluesky, as other tech companies have also encountered similar scrutiny. For example, when Anthropic experienced a leak of its client source code, social media users immediately attributed it to careless vibe coding with Claude Code, despite the company attributing the issue to human error during manual deployment.
Throughout the past year, there have been numerous instances where AI-assisted coding has been blamed for various tech failures, including a significant outage at Amazon and incidents where coding errors led to the irreversible deletion of files. While these examples provide ammunition for critics of AI coding, it is essential to recognize that software glitches existed long before AI tools became prevalent.
Paul Frazee, reflecting on the current state of coding, noted in a March post, "The Bluesky team maintains the same review, red-teaming, and QA processes that we always have. AI coding tools have proven useful but haven’t changed the fundamental practices of good engineering. Human review and direction remain key.”
While some Bluesky users are eager to blame AI tools for every glitch, others urge caution in making such assumptions. Randi Lee Harper, a user, articulated the need for a nuanced conversation about AI-assisted coding, emphasizing that the discourse cannot progress if non-technical users dismiss AI outright.
In fact, even among those who understand that Bluesky's development isn't entirely reliant on AI, there remains an inclination to mock the use of AI tools. Lucyfer, another user, humorously noted, "Is blaming vibe coding for the Bluesky outage plainly wrong? Yes. Is it funny? Also yes." This illustrates how the narrative around vibe coding has become a convenient target for criticism, regardless of the actual technical issues at hand.
Ultimately, the recent outages at Bluesky underscore a larger trend within the tech community—if developers acknowledge their use of AI tools, they may face scrutiny and mockery, regardless of the real cause of any technical difficulties.
Source: Ars Technica News