Fable Took My Job
Rapid advances in AI coding tools are prompting some companies to replace or drastically shrink software engineering teams, leading to anxiety about job security and the future of white‑collar work. Commenters debate whether current models are truly capable of substituting experienced engineers or merely enabling “vibe-coded” but brittle software, and note that management incentives to cut costs and assert control often matter more than technical reality. Broader themes include historical parallels to offshoring and past automation waves, the fragility of U.S.-style employment protections, and speculation about how labor markets, social safety nets, and even capitalism itself might need to adapt if AI continues to erode the value of human knowledge work.
AI replacing engineers and “two‑pizza teams”
- Some argue frontier models already replace many experienced engineers: a tiny human team plus strong LLMs can build and maintain substantial products, especially web apps/SaaS.
- Others say this only applies to “easy” domains; complex, safety‑critical, or deeply technical systems still need human experts who know what not to build.
- Several claim the core job is shifting from “writing code” to “directing AI, QA’ing, and shipping software,” with far fewer humans per product.
On‑call, reliability, and team size
- Skeptics point out tiny AI‑augmented teams can’t realistically cover 24/7 on‑call, handle bus‑factor risk, or maintain institutional knowledge.
- Proponents counter that much on‑call is “support theater,” uptime targets can be met with limited human coverage, and new people can be onboarded with AI help.
Layoffs, labor law, and corporate behavior
- Multiple comments describe harsh, zero‑notice or near‑zero‑notice layoffs (especially in the US), sometimes in deeply personal crises.
- Some see AI as mainly a pretext to cut headcount for cost savings and discipline, not because 10x more output is needed.
- Strong contrast is drawn between weak US protections and stronger European notice/severance norms.
Economic, political, and ethical concerns
- Many frame this as the latest wave of automation, akin to tractors or offshoring, but potentially broader because knowledge work itself is targeted.
- Anxiety about concentration of gains: capital owners capturing AI productivity while labor’s bargaining power collapses.
- Debates over whether new jobs will appear at scale, or whether this time “there may be nothing left to adapt to.”
Executives, managers, and “who gets automated”
- Some note that middle managers and executives are rarely on the chopping block despite tasks that look more automatable than coding.
- Others argue good middle management adds uniquely human value (coordination, conflict resolution, shielding teams) and is harder to automate than code.
Quality, taste, and product direction
- Several threads stress that AI makes “features, not software”: it’s easy to ship more, but hard to maintain coherent vision and taste.
- Tasteful restraint, long‑term product focus, and discerning which customer requests to reject are seen as rising in importance.
Personal responses and mental health
- Commenters describe insomnia, despair, and even suicidal ideation triggered by AI‑justified layoffs and career precarity.
- Some advocate emotional detachment from jobs and financial frugality; others argue this minimizes the real fear of falling into poverty.
- A minority share adaptive stories: moving into trades, repair work, or solo businesses built heavily with AI tools.