The Prompt Went Black
Nobody wrote software anymore. Nobody needed to.
You described what you wanted using natural language, and the model built the app. You could do that in Swahili, or Bengali, or even in Fijian, and it worked.
People who did this for a living still had a job title. They called themselves Software Prompters. None of them had ever opened a line of code, or knew what one even was. Everyone was happily focusing on the prompt, and not on how things worked.
This had been true for so long that it stopped feeling strange. Schools stopped teaching programming languages decades earlier. Universities had turned their computer science labs into training rooms for Prompters. There was no point: the model was always better, always faster, and it never got tired of being asked the same question twice.
Then, on a Tuesday in March, the model stopped answering.
Ravi, who was the head of the Software Prompters Team for an international company, received a call early that morning.
"Ravi, come to the office. Archimedes is down."
The model name was Archimedes 5.7. It had run the world's software for years, in the background, without anyone giving it much thought. Ravi rushed out to see what had happened. Everyone was confused.
He sat down in the meeting room. Prompters tried again. They even tried simpler words. Nothing came back: not an answer, not an error. Not even the usual spinner. The model was gone.
"No panic," said Ravi, while he could feel the sweat on his back. He filled his cup of coffee, and tried again.
At first, this looked like an inconvenience. Chat apps froze mid-sentence. A few websites went blank. Then it reached the infrastructure. Archimedes ran that software every day: it balanced water levels, routed electricity, and decided which line got priority when demand spiked. Prompters only watched the monitors and nudged it with a prompt now and then. The power grid first, and then the water pumps, and finally the gas delivery network, kept coasting on their last settings for a while. Then, one by one, they drifted out of balance and stopped. Within two days, whole cities had no light and no running water.
The company for which Ravi worked decided to close the offices. It was impossible to turn on computers, and the backup generators were going to consume fuel stock.
Ravi tried to call some colleagues, but nobody could fix any of it. The code was broken, and nobody left knew how to read or write code. Every application had been built by the model, from code no human had ever seen. There were no programmers left, only people who knew how to ask.
Raiders of the Last Coder
Two days later, there was an important meeting.
Governments set up emergency committees. The committees did what people do when they run out of ideas: they went digging through old records for someone who still knew how. Ravi was there, with other frightened Prompters. Somewhere in a pension archive, a clerk found a name.
He was a man who had written code by hand, long before Software Prompters existed. He was listed as retired, living somewhere in the Alps. And he had no phone number on file.
It took a search team six days to find him.
Ravi was put on a helicopter, for a long journey, and they had to walk for almost a day in the woods. And finally they saw him, sitting outside to enjoy the sunset with a cup in his hands.
His name was Nestore. He was in his eighties, living alone in a stone house near the tree line, in the Swiss Alps, far from any town. He grew his own vegetables, and drank water from a local spring. He kept no screens in the house at all.
"Who are you?"
The team explained why they had come. Nestore did not look surprised. He listened to the whole story without interrupting.
The Man in the High Valley
"I can't help you," he said, when they finished.
Ravi got upset.
"Why can't you, sir? It is a tragedy: the hospitals are running on generators, there is no water, and families have no heat."
He nodded through all of it. Then he pointed at his own eyes.
"I went blind twelve years ago," he said. "I can't read a screen. I can't read a page of code, not even with my hands on the keys. Whatever I once knew is still in my head, somewhere, but I have no way to get it out."
One of the team burst into tears.
"But you could dictate it, sir," Ravi suggested. "You can describe the logic out loud and we can type it. It will take time, we know, but it may work."
"Maybe," he said. "But even if I could, you'd be asking me to rebuild, from memory, something I haven't touched in thirty years. I stopped being part of this world on purpose. I didn't retire up here by accident: I came here because the work didn't need me anymore, and I was tired of pretending that it still did."
They looked at each other, disheartened.
"The world moved on from people like me a long time ago. It can move on without me now. That already happened, for other things and for other people. It will find a way, or it won't. I don't mind. It was never really my decision to make."
Ravi sat down on a tree trunk that served as a seat.
Nestore offered them some wine, food and a place to sleep before the long walk back down. Nobody argued with him.
The team left the next morning, empty-handed, back toward the cities with no light and no water.
What happened next? Nestore never knew, but he still enjoys the sunset with a cup of tea, while listening to the birds in the woods.
This is fiction. Plenty of developers already work mostly by describing what they want, and almost all of them still understand what comes back and can fix it by hand when it breaks. Take that second half away and you get Nestore's world.
We are not there yet. It is closer than it was five years ago.
Top comments (0)