Copilot Is Everywhere in the Conversation, but Developers Have Stopped Agreeing on What It's For

A solo developer just hit $200k ARR with four utility apps and no team. An 11-year-old shipped an open-source AI agent platform. On r/SaaS, these stories circulate as proof of a genuine threshold crossed — the barrier to entry didn't just lower, it effectively dissolved. The posts read less like hustle porn and more like field reports from a different era of software, one where the leverage available to a single person with a good problem and access to Cursor or Copilot exceeds what a funded team could do five years ago.

But a parallel conversation is running on Bluesky that refuses to celebrate. One post, citing METR's peer-reviewed research on developer productivity, put it bluntly: AI assistance makes you slower, makes you understand your code less, and produces more bugs. This isn't a vibe or a career-anxiety post dressed up as critique — it's pointing at controlled studies, and it keeps getting reshared in circles where people read footnotes. The tension isn't between AI optimists and Luddites. It's between two groups who have genuinely different empirical experiences, and neither is obviously wrong.

Copilot's prominence in the conversation right now is striking less because of praise and more because of the specific frustrations it's generating. The r/cursor community is griping about the IDE resetting model preferences every session — a small thing that reveals something larger about whose convenience these tools are designed for. When a developer sets a preference and the tool overrides it silently, the implicit message is that the product team's defaults matter more than the user's judgment. That's an old complaint in software, but it lands differently when the tool is supposed to be an intelligent collaborator.

The craftsmanship thread is the one worth watching. Hong Minhee's essay on craft-lovers losing their craft circulated across Bluesky, Lobsters, and Hacker News simultaneously — a rare cross-pollination that usually signals a nerve got hit. The argument isn't that AI produces bad code. It's that the act of wrestling with a problem, understanding it deeply enough to solve it well, is being automated away before developers realize what they're giving up. One Bluesky post cut to the same point without the essay: "The only skill left that matters? Understanding the actual problem." That's either a liberating reframe or an epitaph for a profession, depending on your read, and right now both readings are live in the conversation at the same time.

What's clarifying in the data is where enthusiasm concentrates. YouTube and mainstream news are running warm — tutorials, launches, capability demonstrations. Reddit is more mixed but broadly constructive, full of builders asking practical questions and sharing what works. Bluesky is where the structural critiques live, not because Bluesky is contrarian by nature but because that's where the developers who read research papers and write long-form essays tend to post. The platforms aren't covering the same story. They're covering adjacent stories about the same tools, and the gap between them is widening as the tools mature and the stakes get clearer. Solo developers will keep shipping. The METR findings will keep circulating. At some point the industry will have to decide which number it's optimizing for.