Is Bluesky Down? The Rise of ‘Vibe Coding’ and AI Blame in Tech

The use of AI coding tools has quickly become a convenient scapegoat for any tech issue. Recently, social network Bluesky experienced intermittent service disruptions. While not unusual – Bluesky has faced similar issues before, coinciding with problems on other platforms – the reaction was notable. Many users immediately blamed “sloppy, AI-assisted ‘vibe coding’” by the Bluesky development team.

During Monday’s outage, Bluesky feeds were flooded with posts accusing developers of relying on unreliable AI tools to ship faulty code. Memes, ironic comments, and outright anger filled the platform. As Bluesky user T-Kay succinctly put it, “Any developer using ‘vibe-coding’ or relying on AI to code is too stupid to do the job and should be fired.”

This reaction highlights a broader trend: many tech users are instinctively repulsed by the idea of AI involvement in the products they use. Despite increasing enthusiasm among professional coders, many end-users view AI coding tools with suspicion.

Bluesky’s Openness About AI Use

The backlash wasn’t entirely unexpected. Bluesky’s team had already faced criticism for admitting their use of AI tools. Founder Jay Graber openly stated in March that “Bluesky is made with AI,” specifically mentioning the use of Claude Code. Technical Advisor Jeromy Johnson (known as “Why” on the site) has been a vocal proponent, claiming Claude wrote 99% of his code in the past two months. Even CTO Paul Frazee jokingly admitted to “vibecoding.”

The launch of Attie, a side project allowing users to build custom Bluesky feeds with a Claude Code-powered chatbot, further fueled concerns. While Attie is separate from the core app, some users saw it as a worrying distraction and unwelcome AI integration, especially given Bluesky’s promise not to use posts for AI training.

Graber responded to the uproar, emphasizing that the goal is to empower users, not generate content. “Attie uses AI to help you create custom feeds without having to know how to code,” she explained.

A Pattern of Blame

The Bluesky outage isn’t an isolated incident. Similar blame was directed towards “vibe coding” when Anthropic accidentally leaked client source code, despite the error being attributed to human error during deployment. Sloppy AI coding has also been blamed for outages at Amazon and file deletions. Concerns about security and reliability further contribute to the skepticism.

However, attributing every glitch to AI is presumptuous. As Paul Frazee points out, software bugs existed long before AI. He emphasizes the importance of distinguishing between amateur use of AI to generate brittle code and experienced developers using AI tools to enhance efficiency while maintaining rigorous review and quality assurance processes.

The Nuances of ‘Vibe Coding’

The term “vibe coding” originally described non-coders using AI to create minimally functional, yet fragile, code. This differs significantly from experienced developers leveraging AI to streamline their workflow. As Ars Technica noted in a recent deep dive, humans remain essential to the software development process.

Ultimately, even those who understand the nuances of AI-assisted coding may find the opportunity to mock developers amusing. As one Bluesky user put it, blaming vibe coding is funny, even if it’s inaccurate. The lesson, as one user pointed out, is that admitting to using AI may mean losing the benefit of the doubt.

Source: Ars Technica