Somehow, they have to convince you that an AI can do your workers' jobs. One way to sell that pitch is to fire a *ton* of Amazon workers and announce that their jobs have been given to a chatbot. This isn't a production strategy, it's a marketing strategy - it's Amazon deliberately taking an efficiency loss by firing workers in a desperate bid to convince you that you can fire *your* workers:

pluralistic.net/2025/08/05/ex-…

6/

Amazon *does* use a lot of AI in its production, of course. AI is the "digital whip" that Amazon uses to allow itself to control drivers who (nominally) work for subcontractors. This lets Amazon force workers into unsafe labor practices that endanger them and the people they share the roads with, while offloading responsibility onto "independent delivery service" operators and the drivers themselves:

pluralistic.net/2025/10/23/tra…

7/

Amazon leadership has announced that AI has or will shortly replace its coders as well. But chatbots can't do software engineering - sure, they can write code, but writing code is only a small part of software engineering. An engineer's job is to maintain a very deep and wide context window, one that considers how each piece of code interacts with the software that executes before it and after it, and with the systems that feed into it and accept its output.

8/

There's one thing AI struggles with beyond all else: maintain context. Each linear increase in context that you demand from AI results in an *exponential* increase in computational expense. AI has no object permanence. It doesn't know where it's been and it doesn't know where it's going. It can't remember how many fingers it's drawn, so it doesn't know when to stop. It can write a routine, but it can't engineer a system.

9/

When tech bosses dream of firing coders and replacing them with AI, they're fantasizing about getting rid of their highest-paid, most self-assured workers and transforming the insecure junior programmers leftover into AI babysitters whose job it is to evaluate and integrate that code at a speed that no one - much less a junior programmer - can meet if they are to do a careful and competent job:

bloodinthemachine.com/p/how-ai…

10/

AI Killed My Job: Tech workers

Tech workers at TikTok, Google, and across the industry share stories about how AI is changing, ruining, or replacing their jobs.

^{Brian Merchant (Blood in the Machine)}

The jobs that *can* be replaced with AI are the jobs that companies already gave up on doing well. If you've already outsourced your customer service to an overseas call-center whose workers are not empowered to solve any of your customers' problems, why not fire those workers and replace them with chatbots? The chatbots also can't solve anyone's problems, and they're even cheaper than overseas call-center workers:

pluralistic.net/2025/08/06/unm…

11/

Amazon CEO Andy Jassy wrote that he "is convinced" that firing workers will make the company "AI ready," but it's not clear what he means by that. Does he mean that the mass firings will save money while maintaining quality, or that mass firings will help Amazon recoup the $180,000,000,000 it spent on AI this year?

12/

Bosses *really* want AI to work, because they *really, really* want to fire you. As Allison Morrow writes for *CNN* bosses are firing workers *in anticipation* of the savings AI will produce...someday:

cnn.com/2025/10/28/business/wh…

All this can feel improbable. Would bosses really fire workers on the promise of eventual AI replacements, leaving themselves with big bills for AI and falling revenues as the absence of those workers is felt?

13/

The answer is a resounding *yes*. The AI industry has done such a good job of convincing bosses that AI can do their workers' jobs that each boss for whom AI fails assumes that *they've* done something wrong. This is a familiar dynamic in con-jobs.

14/