Fable Took My Job
- ID
- 34592
- Status
- summarized
- Published
- 12 Oct 2026, 4:30 PM
- Fetched
- 13 Oct 2026, 1:39 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://cendyne.dev/posts/2026-10-11-fable-took-my-jorb.html
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.0
- Created
- 13 Oct 2026, 1:39 AM
- Tags
- Audience
- developersvibe_coderssaas_startup_founders
What happened
A personal essay from cendyne.dev describing a layoff the author attributes to economics rather than capability: as the last engineer, they were replaced because an LLM at 'Fable/Mythos tier' of marketed intelligence was cheaper than their compensation, and leadership reportedly felt confident enough to coast until an M&A. The author also reports six or seven people in a DevOps interest group receiving layoffs or notices in the last month, a hiring manager who interviewed them being laid off a week after a CEO posted an 'AI is changing how we develop software' article, and a team offshored after AI assistance raised the output of less experienced, lower-cost staff. Their stated conclusion is that frontier models are still not good enough to replace an experienced engineer. The Hacker News thread drew 212 points and 320 comments.
Why it matters
The concrete claim worth acting on is not 'AI replaced an engineer' but the cost comparison: a single model subscription priced against one senior salary, plus AI assistance raising throughput of less experienced staff, is being used to justify both headcount cuts and offshoring decisions. If you are a founder or lead deciding team shape this quarter, that means your junior-to-senior ratio and your onshore/offshore split are now live cost levers that executives will pull with or without engineering input — so get ahead of it by documenting which work actually requires senior judgment versus which is throughput work that AI plus cheaper staff can absorb. For individual developers, the essay's specifics (a role eliminated with the company heading to M&A, a hiring manager cut one week after running interviews) are a reminder that hiring signals and 'we're growing' messaging can invert within days; keep your own pipeline warm rather than reading stability from a signed offer or a healthy roadmap.
Discussion angle
If AI assistance genuinely raises the throughput of less experienced and cheaper staff, does that make senior-heavy teams harder to justify on a spreadsheet — and what work in your own codebase would you defend as needing senior judgment rather than throughput?