What's gone wrong with AI & labor — a thought experiment

@random_walker
ENGLISH1 day ago · Jul 28, 2026
319K
1.2K
124
37
1.1K

TL;DR

Arvind Narayanan uses a thought experiment to show that AI's impact on labor depends on whether it's trained on the creative process or just the final output, arguing for tools that augment rather than automate.

A thought experiment that I think helps explain much of what’s gone wrong with AI and labor:

Imagine an alternate universe in which — for whatever reason — no one ever published source code online. The open source movement or even the concept of open source didn’t exist. Naturally, LLMs wouldn’t be good at coding, because they wouldn’t be trained on vast code datasets.

What this alternate universe does have, just like our actual universe, are public software binaries — tens of petabytes worth, vastly greater than the scale of today’s frontier LLM training datasets. So at some point in the scaling of these LLMs, imagine that they start to get good at producing complete working applications from specifications — but skipping the source code generation step entirely. AI-generated software would be shitty and inelegant and insecure but AI companies would constantly promise that the next bigger model would make it all better.

In this universe, software-generating LLMs compete directly with software engineers. Binaries are not human readable. They are equally inscrutable to software engineers and non-technical people. Over time, an increasing fraction of software would be vibe-rolled (not vibe-coded — there is no code!) It is not as good as human-authored software, but it’s free to generate! Since there is no source code, having a software engineer involved in the process adds nothing (except cost). Even to the extent that AI-generated software creates new demand for labor because of its limitations, it doesn't require highly paid software engineers and can instead be handled by lower-skill workers (perhaps just repeatedly yelling at the LLM to make no mistakes).

In short, human authoring and AI generation are two parallel ways of getting to the same output. Software engineers and AI are substitutes, not complements. AI doesn’t help software engineers amplify their abilities, and software engineers bring no skills to supervise AI any more effectively than non-engineers can. In this world, AI would feel alienating and terrifying for software engineers.

You probably know where I’m going with this. In our actual timeline, artists and many other professionals experience AI in a way that resembles this dystopia. In many non-software domains, the finished products of human creative endeavors are readily available to train on, but almost nothing that goes into making them. So AI tools aren’t of much help during the creative process. They merely mimic and substitute.

A different outcome is possible. The positive vision that’s not widely appreciated outside the tech world is that coding agents have given software engineers superpowers. We work together with our agents; complex software is produced over the course of thousands of alternating turns between human and agent. The narrative that coding agents are replacing engineers has so far turned out to be bunk. The lived experience of using agents closely matches Simon Willison’s table saw metaphor (“Quitting programming as a career right now because of LLMs would be like quitting carpentry as a career thanks to the invention of the table saw.”). The barrier for starting to work with a new programming language, framework, or codebase has dropped a hundredfold because coding agents are also teaching agents (software developers use agents to understand code more often than to generate it).

Open-source software and culture is a historical accident. We take it for granted that not only are the outputs of software engineers’ creative work available publicly, but so are all of the intermediate steps (specifications, plans, mockups), tacit knowledge (StackOverflow, documentation culture), detailed process traces (issues, pull requests, bug fixes, code reviews), collaboration records (version control, project boards), and more broadly a culture of learning in public. This level of explicit description would be completely alien in most professions.

Many companies are investing heavily into capturing tacit knowledge, process traces, and other components of this missing middle. Ironically, they are doing this in the pursuit of even more automation. My thesis, contrary to seeming common sense and all the money being invested, is that this wave of AI can ultimately be more helpful for augmenting workers than for automating them away. With the right scaffolds, models trained to deeply understand how creative workers arrive at their outputs will be able to collaborate with them, empowering them and amplifying their potential. If the industry recognized this, it would be a big win both economically and politically.

Remix in YouMind

Turn one viral article into a full content workflow

Collect the source, decode the pattern, create assets, draft the story, and distribute from one AI workspace.

Explore YouMind
For creators

Turn your Markdown into a clean 𝕏 article

When you publish your own long-form writing, images, tables, and code blocks make 𝕏 formatting painful. YouMind turns a full Markdown draft into a clean, ready-to-post 𝕏 article.

Try Markdown to 𝕏

More patterns to decode

Recent viral articles

Explore more viral articles