Bluesky Users Blame Bugs on Vibe Coding
▼ Summary
– Bluesky experienced service disruptions on Monday, which the company attributed to an upstream service provider issue.
– During the outage, many users blamed the problems on developers using unreliable AI-assisted “vibe coding” to write faulty code.
– The user reaction reflected a broader reflexive repulsion among some tech users toward the use of AI tools in product development.
– This contrasts with growing enthusiasm for AI coding tools among professional software developers.
– Prior to the outage, Bluesky’s development team had openly discussed their use of AI tools like Claude Code in their work.
A recent service disruption on the social platform Bluesky sparked a revealing backlash, highlighting a deep-seated skepticism toward AI-assisted development. While the company attributed Monday’s intermittent issues to an upstream provider, a significant portion of its user base immediately pointed fingers at a different culprit, vibe coding. The term, used derisively, refers to the perceived practice of relying on AI tools to generate sloppy or unreliable code.
User feeds quickly filled with posts, memes, and ironic commentary blaming the development team for shipping faulty software built with AI assistance. The sentiment among critics was often one of sharp condemnation, framing the use of such tools as a fundamental lack of skill. One user’s post captured the prevailing anger, stating that any professional relying on AI to code demonstrates incompetence and should be removed from their position, arguing that programming requires genuine expertise, not automated guesswork.
This collective reaction underscores a persistent cultural divide. Even as professional coders increasingly embrace powerful AI coding assistants to boost productivity, a vocal segment of end-users remains deeply distrustful. For them, AI represents a convenient scapegoat for any perceived flaw or failure in the digital products they use daily, a reflexive boogeyman for the tech industry’s ills.
The controversy didn’t emerge in a vacuum. Bluesky’s team has been openly discussing their use of these tools, which likely primed users for this specific blame. Earlier this year, founder Jay Graber stated plainly that Bluesky is made with AI, noting that engineers and even some non-engineers use Claude for coding tasks. Similarly, technical advisor Jeromy Johnson has been a vocal advocate, revealing that an overwhelming majority of his recent code was AI-generated. His February comment, that “things are changing fast,” now reads as a prescient acknowledgment of the rapid, and often contentious, shift in software development practices. The outage simply provided a flashpoint for simmering user anxieties about this accelerating transformation.
(Source: Ars Technica)
