When Technology Becomes Literature
Not how literature answers technology, but whether technology can become literature¶
One question kept returning today:
In an age of technology, why does literature matter at all?
A few days ago I read Mark William Roche's essay on why literature matters so much in a technological age (Chinese text; the argument is laid out at length in his book Why Literature Matters in the 21st Century). The further I read, the more it seemed to echo, at an odd angle, what Above The Clouds has been trying to do.
Roche's starting point is clear. A technological age prizes efficiency, calculation, function, optimization, results. Is it useful? Is it faster, cheaper, measurable, on target? Those questions have become modern society's most natural way of thinking.
Technology itself is not the problem. The problem is that once means–end reasoning keeps expanding, people get pulled into the same system.
A person is measured by income.
A job, by title.
A paper, by citations.
A book, by sales.
A student, by scores.
An engineer, by output.
A model, by benchmark.
In the end, even a life starts to look like it ought to have an explicit objective function.
Roche's answer is that this is exactly where literature earns its place. It keeps reminding us that some things matter not because they are useful.
Friendship has no KPI.
Memory has no yield.
Love has no benchmark.
Remembering, at dusk, a mouthful of spring water from childhood produces nothing.
And yet these may be what a life is made of. His question, roughly: the stronger technology becomes, why does literature matter more? His answer: literature keeps what the logic of efficiency cannot fully swallow.
It is a strong answer. But today I realized that what Above The Clouds is really after is not quite the same thing. Roche asks how literature faces technology. The question I care about is the other one:
Can technology itself become literature?
Subject Is Not Enough¶
Writing about programmers does not make technology into literature. Neither does writing about AI. GPUs, models, self-driving cars, Silicon Valley, algorithms, cloud computing — these only show that technology has entered the story. It may be nothing more than scenery:
He opens his laptop.
The GPU fans roar.
The model starts training.
He looks out the window and thinks of home.
Swap the GPU for a car and nothing breaks:
He starts the car.
The engine roars.
The car pulls onto the highway.
He looks out the window and thinks of home.
If the technology can be swapped out and the story barely changes, the technology is backdrop. That is literature writing about technology — not yet technology becoming literature.
Experience Has Changed¶
Someone who actually lives inside technical systems does not have a nineteenth-century life with better tools. Time, space, causality, power, and the relation between a person and the world have all shifted.
A model leads today and is obsolete in a few months. A project years in the making disappears in one strategy review. A team is built, then dissolved in a reorg. Code runs somewhere you never see and touches millions of requests. An error no longer has to come from any one person; it hides in a node of a distributed system, in the data, in a dependency, somewhere among dozens of services.
People used to face people. More and more, people face systems.
Traditional literature is superb at fathers and sons, husbands and wives, rulers and ministers, friends and enemies. But modern lives are increasingly redirected by something with no face:
| What decides | What it decides |
|---|---|
| Algorithms | what you see |
| Hiring pipelines | who reaches the next round |
| Org charts | who belongs to which team |
| Capital | which project survives |
| Metrics | which design is kept |
| An acquisition | the paths of tens of thousands of lives |
There may be no villain here, maybe not even anyone who truly made a decision. But a life has changed course.
Kafka wrote bureaucracy. Industrial-age fiction wrote the factory. Modernism wrote the city. The AI age should have its own literary experience: how models, algorithms, platforms, capital, organizations, data, and systems together enter one person's fate.
From Eye to Sensor¶
As a child I saw mountains, spring water, mud walls, stones, trees, fields. The world was direct: you looked, and the mountain was there.
Then came computers, and the world became data. Then self-driving cars: images, video, point clouds. Sensors saw the world first, models interpreted it, and the person stood somewhere behind. With AI the world became embeddings, representations, probabilities, predictions.
Then: eye → mountain.
Now: sensor → data → model → world.
It looks like ordinary technical progress. Seen as literature, it is an enormous change: the way a person understands the world has been mediated, layer by layer, by technology. And that raises a real question:
When machines get better and better at seeing the world, how does a person still see it?
That is no longer an engineering question. It has become a literary one.
The Cloud Is No Longer Just a Cloud¶
In the book I wrote:
Capital never rests.
Neither do the clouds.
Why does that line hold? Not because "cloud computing" is a fresh phrase, but because the word cloud has changed underneath it. It is the cloud I looked up at as a child; it is the cloud I later worked on; it is a vast system that runs without pause. The childhood cloud drifts past. The technological cloud cannot stop.
A technical term slowly becomes a literary image, holding nature, machinery, capital, and human fate at once. That may be one small instance of technology becoming literature: technical language loses its purely instrumental role and starts to carry memory, metaphor, time, and fate.
Life in Versions¶
Technology may change not only what literature is about but its form. Traditional novels tend to run on continuous time: childhood, youth, marriage, middle age, old age. A technologist's life may unfold more like:
Version 1. Version 2. Reorg. Acquisition. Shutdown.
New model. New company. IPO. Layoff. AI.
A stretch of life can end without a full stop — just a system no longer maintained, a repo archived, a team gone, a product sunset. Then the next version begins.
If that discontinuity enters the form of the writing — short sentences, jumps, white space, abrupt cuts from one scene, one company, one era to the next — then technology is no longer only what the work says; it shapes how the work is written. Thinking this through, I suspect the short sentences and line breaks of Above The Clouds were never purely an aesthetic choice. They match the world I actually lived through. A life is not a smooth curve; it is closer to a system that is deployed, rolled back, migrated, and refactored.
Not Science Fiction¶
Science fiction usually asks: if technology reaches some point, what becomes of us? Conscious AI, robots replacing people, colonies on Mars — reasoning forward from now.
What interests me is different:
The technology has already happened.
What did a person living inside it actually go through?
Not the future, but technological history already lived. Not prediction, but memory. In that sense Above The Clouds is not only my life; it also tries to preserve a period's lived technological experience.
Two Different Roads¶
Roche's logic runs:
technology grows stronger → instrumental reason grows stronger → literature matters more
Literature guards what cannot be quantified or optimized. That is literature transcending technology.
The road I keep finding myself on runs the other way:
technology → human experience → memory → language → literature
Not standing outside technology saying it is too cold, so we need literature — but walking inside it. Writing models, systems, capital, companies, organizations, incidents, data, AI. Then, once all of that has passed through one person's life and become memory, asking: what are they, finally? Perhaps the answer is still literature.
| Roche | This book | |
|---|---|---|
| Question | How does literature transcend technology? | How does technology enter literature? |
| Stance | Outside, as counterweight | Inside, as lived material |
| Endpoint | Protect the unquantifiable | Turn the technical into memory |
A Question, Not a Genre¶
I now prefer this phrase to "technology literature." The latter sounds like a new genre, and a genre invites border disputes at once: does science fiction count, cyberpunk, programmer novels, industrial fiction, tech journalism? There is no need to stake out a label this early.
"When technology becomes literature" is not a category but a question:
Can technology be not only literature's subject,
but enter perception, memory, language, metaphor, and narrative form,
and in the end become literature itself?
I increasingly think it can. A few tests:
- Delete the technology — is the story still the same?
- Does the technology actually change a character's fate?
- Does it change how a person looks at the world?
- Has technical language turned into literary image?
- Does the technology, in the end, come back to the person?
Explaining how a system works is still technical writing. If, after the system is written, what we see is ambition, loss, memory, friendship, choice, fate, and time — then it has entered literature.
Closing¶
Having thought this far, I understand better what Above The Clouds should be. Not a case for how important AI is, not proof of how advanced technology has become, not even a record of which companies I worked at on which projects. Those are the surface. What deserves to last is how, after decades lived inside technology, technology entered one person's memory.
The spring in the mountain village was real; so is the point cloud. My father was real; so are the models. The mud walls of childhood were real; so are the data centers. They belong to the same life — so why should one side belong naturally to literature and the other only to technical documentation?
Technology ages. Systems go offline, models go stale, companies vanish, code goes unmaintained. What remains is memory — and once memory is written down, technology has become literature.