Fable and Layoffs: Why One Engineer Says AI Eliminated His Job Without Beating Him

An engineer who was the last of his team to be let go has written that Fable, an AI model, did not take his job by being better. It did so by being cheaper than his compensation. Management, he says, gained enough confidence that a lower-cost model could carry the product until an acquisition. The account draws a line between AI replacing a worker and AI contributing to a role being eliminated.

What the engineer describes

The post, published on the personal site cendyne.dev, is a first-person account of being laid off after Fable came into use at the company. The author was the last engineer remaining.

The central claim is not that Fable outperformed him. It is that cost drove the decision: a model priced below an engineer's pay gave leadership the belief that the company could coast through to an acquisition. This is one person's experience, and the company's internal reasoning has not been independently verified.

Replacement versus role elimination

The author prefers the phrase that AI contributed to the elimination of his role over the more common claim that AI took his job. The distinction matters.

Replacement implies an AI doing the same work at the same quality. Elimination only requires that someone decides the work can be done at lower quality, less often, or not at all, and that the savings are worth it. Under that logic, a model does not need to pass any benchmark that matches a senior engineer. It only needs to be good enough for the next few quarters at a fraction of the price.

Where this fits

Stories like this have been building. We covered Open Executive, the open-source virtual executive team built by developers who were pushed out to make room for AI. That project answered layoffs with satire, arguing that executives are expensive and automatable too. This post is less symbolic and more personal: no tool, just an account of how a cost calculation looked from the receiving end.

Why the acquisition detail matters

The mention of a pending acquisition is worth separating from the AI question. Companies heading into a sale have long had reasons to cut spending and keep the product stable enough to show well. AI offers a new way to do that, since it lets a business keep a codebase running with fewer people on payroll.

That creates a plausible risk, and this is speculation rather than something the post demonstrates. Due diligence in an acquisition often looks at how well the engineering is understood and documented. If the people who understood the system are gone and a model has been maintaining it, the buyer may inherit costs that never showed up in the savings estimate.

What changes for different groups

Engineers. Being better than the model may not be the whole story. Roles that look like stable maintenance, with few changes and a single owner, are the easiest to justify cutting on cost alone. Work tied to accountability, such as incident response, security and data handling, is harder to hand over because someone has to answer when it fails.

Engineering managers and founders. The cheap-model decision should be tested against what leaves with the person: system knowledge, on-call coverage and context about past decisions. Those rarely appear in a cost spreadsheet but surface later.

Hiring markets. The more visible effect may not be dramatic layoffs but quieter ones: hiring freezes, contractors not renewed and junior openings that never get posted. That is an inference from the cost logic described, not a measured trend.

Takeaway

The useful question for the industry is not whether AI can do an engineer's job as well, but who decides what level of quality is acceptable and who bears the cost when it falls short. This account suggests that price, not capability, can be the deciding factor, and that is harder to argue against with better code.

Reference: https://cendyne.dev/posts/2026-10-11-fable-took-my-jorb.html