Bluesky users are mastering the fine art of blaming everything on "vibe coding"

2026-04-07 · Source: AI - Ars Technica · Field: Technology & Digital — Software Development & Engineering, Artificial Intelligence & Machine Learning, Cybersecurity & Data Privacy · Depth: Intermediate, medium

Summary

Bluesky experienced intermittent service disruptions on Monday, April 7, 2026, which the company officially attributed to an "upstream service provider." However, many Bluesky users immediately blamed the outage on "vibe coding," a term used to describe sloppy, AI-assisted development. This reaction highlights a broader user repulsion towards AI tools in product creation, contrasting with professional coders' increasing enthusiasm for AI coding assistants. Bluesky founder Jay Graber and Technical Advisor Jeromy Johnson have openly stated their team's use of AI tools like Claude Code, with Johnson claiming Claude wrote 99% of his code in two months. Public concern escalated with the announcement of Attie, an AI-powered side project for custom feeds, despite Bluesky's 2024 promise not to use user posts for AI training. This incident follows other tech snafus, including an Anthropic source code leak and Amazon outages, also attributed to "vibe coding" by some social media users, even when human error was cited.

Key takeaway

For CTOs and VP of Engineering considering AI coding tools, understand that public perception can quickly attribute any service disruption to AI-assisted development, regardless of the actual cause. Your teams should proactively communicate the rigorous human review and quality assurance processes in place for AI-generated code to maintain user trust and avoid being the default "boogeyman" for system failures.

Key insights

User perception of AI-assisted coding as inherently flawed creates a default blame for tech issues.

Principles

• Human oversight remains essential in AI-assisted software development.
• Distinguish between amateur "vibe coding" and professional AI-assisted development.

In practice

• Implement robust review and QA processes for AI-generated code.
• Communicate AI tool usage transparently, clarifying roles and safeguards.

Topics

• Bluesky
• AI Coding Tools
• Vibe Coding
• Service Disruptions
• Public Perception of AI

Best for: CTO, VP of Engineering/Data, Director of AI/ML, Software Engineer, AI Engineer, Tech Journalist

Related on AIssential

• Vibe coding and agentic engineering are getting closer than I'd like — The increasing reliability of AI coding agents blurs the distinction between casual "vibe coding" and professional "agentic engineering."
• You’re Shipping Code You Don’t Fully Own Anymore — AI-assisted "vibe coding" accelerates development but introduces hidden costs and systemic risks due to reduced understanding of generated infrastructure and code.
• How Sustainable is Vibe Coding? — AI's true value in coding lies in augmenting experienced developers, not replacing foundational understanding for novices.
• Breaking the Spell of Vibe Coding — Vibe coding can induce a "dark flow" state, similar to gambling, leading to misperceptions of productivity and skill development.
• When Your Vibe Coded App Goes Viral—And Then Goes Down — AI-driven "vibe coding" enables rapid app development, but human engineers are crucial for quick debugging.
• Vibe Coding Isn’t the Problem. Not Understanding the Stack Is. — Understanding the full system stack, beyond application code, is critical for safe and effective AI-assisted development.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by AI - Ars Technica.