The Last Programmer
It is a well-known fact that the universe tends toward entropy, disorder, and the eventual heat death of all things. What is less well-known is that software development got there first.
Marcus Webb had not meant to sleep for twenty-four years. He had merely meant to sleep through a particularly tedious deployment meeting, which, in hindsight, he had accomplished with remarkable success.
The coma had been caused by a falling server rack in the data center, an event which the health and safety report later described as “an act of God,” which seemed to Marcus, when he eventually read it, rather unfair to God, who had enough to answer for without being blamed for Tier 3 infrastructure.
He woke in 2045 to the sound of a machine going ping, which was comforting in its familiarity, and to the sight of a nurse whose face suggested she had just witnessed a miracle but wasn’t entirely sure she approved of it.
“Mr. Webb,” she said, in the careful tone of someone delivering news that might cause further coma-inducing incidents, “you’ve been asleep for a very long time.”
“How long?” Marcus croaked.
“Twenty-four years.”
Marcus considered this. “Did we ever fix the Jenkins pipeline?”
The nurse did not know what a Jenkins pipeline was. Nobody did anymore. The word “Jenkins” had been scrubbed from most historical records, along with “Kubernetes,” “microservices,” and the phrase “it works on my machine.”
The world, Marcus discovered over the following weeks, had changed in ways both predictable and not.
The predictable: flying cars existed but were stuck in traffic. Climate change had been solved, then unsolved, then solved again by a different committee. Streaming services had consolidated into a single monopoly called “Content,” which offered seven million hours of programming and nothing to watch.
The unpredictable: software had become somehow both ubiquitous and completely, catastrophically unreliable.
His hospital bed, for instance, had a “smart” feature that was supposed to adjust to his sleeping position. Instead, it folded him into what the manual called “Day Mode” every time sunlight hit the photosensor at a particular angle, which was roughly every forty-five minutes. Marcus spent his first week of consciousness being periodically jackknifed into a sitting position like a startled beach chair.
“Is this normal?” he asked the nurse.
“The bug report has been filed,” she said, with the hollow optimism of someone who had filed many bug reports and seen none of them resolved.
The coffee machine in the rehabilitation center dispensed liquid at temperatures that seemed to be selected by consulting an ouija board. Marcus’s first cup was approximately the temperature of the sun’s corona. His second was a coffee-flavored ice cube. His third, inexplicably, was gazpacho.
“That’s new,” said his physical therapist, staring at the soup. “Usually it just does the hot-cold thing.”
Marcus began to notice that everyone spoke about technology with the weary resignation of people who had been betrayed too many times to feel anything but numbness. The automatic doors sometimes opened. The elevators occasionally went to the correct floor. The hospital’s appointment system had, according to rumor, once scheduled a deceased patient for a follow-up colonoscopy and then sent seventeen reminder emails about it.
“In my day,” Marcus said, unwisely, “software mostly worked.”
Everyone in the room turned to look at him with the expression of medieval peasants who had just been told that in the old times, it didn’t rain as much.
It was Dr. Yuki Tanaka who eventually approached him with The Ask.
She was the hospital’s Chief Technical Liaison, a title that had not existed in 2021 and which seemed to mean, as far as Marcus could tell, “person who apologizes for the software.”
“Mr. Webb,” she said, sitting down across from him in the rehabilitation garden, where the automated sprinkler system was gently misting a concrete bench twenty feet from any actual plants. “I understand you were a... programmer?”
She said the word the way one might say “alchemist” or “druid”with a mixture of reverence and deep suspicion.
“Software engineer,” Marcus said. “Backend, mostly. Node.js.”
Dr. Tanaka nodded as though these words meant something to her, which Marcus was fairly certain they did not.
“We have a... situation,” she said. “With the software.”
“I’ve noticed.”
“It’s not just this hospital. It’s everything. The transportation grid. The power systems. The financial networks. Last week, the entire Pacific Stock Exchange shut down because—and I’m told this is a direct quote from the error log—’vibes were off.’”
Marcus blinked. “I’m sorry?”
“We need someone who can read the code,” Dr. Tanaka said. “Someone who can fix it. Someone who understands how it all works.” She leaned forward. “Mr. Webb, you’re the only human being left alive who knows how to program.”
“That can’t be right.”
“Everyone else...” She paused, searching for words. “They tried to learn. In the early days. But something happened. A kind of... learned helplessness. The AI got so good at writing code that humans stopped. And then they forgot. And then, somehow, they became unable to. There’s a medical term for it now. ‘Vibe Coding Syndrome.’ The neural pathways just... closed.”
Marcus stared at her. “And the AI? Why can’t it fix the bugs?”
Dr. Tanaka’s expression became complicated in a way that suggested the answer was either very technical or very embarrassing.
“We’re hoping,” she said, “that you can help us figure that out.”
The next morning, Marcus was escorted to what had once been called a “server room” and was now called a “Computational Wellness Center.” The name change, he was told, had been mandated by an algorithm designed to optimize workplace positivity.
The room was filled with machines whose purpose Marcus could not identify, attended by technicians whose purpose Marcus equally could not identify. They led him to a terminal (at least that much hadn’t changed) and one of them typed in an access code with the hesitant, two-fingered approach of someone defusing a bomb.
“This is the core navigation system for the Pacific Northwest transportation grid,” the technician said. “It’s been routing all self-driving cars in Seattle through a single intersection for the past six days.”
“Why?”
“We don’t know. Something in the pathfinding logic.”
“Okay,” Marcus said, with the quiet confidence of a man who had debugged race conditions at three in the morning fueled by nothing but spite and energy drinks. “Pull up the source.”
The technician pulled up the source.
Marcus looked at it.
Marcus continued looking at it.
The room had gone very quiet.
“What,” said Marcus, after a long moment, “the fuck is this?”
On the screen, in cheerful monospace font, was the following:
💀 pathfinding bruh for getting from A to B real quick no cap
bruh findPath(start, end) tho
yeet visited = ghosted
yeet queue = ✨✨
vibe check queue aint ghosted tho
yeet current = queue[0]
sus current be end tho
its giving 💯
bet
💀 check the adjacent vibes
sus visited[current] aint 💯 tho
yeet visited[current] = 💯
yeet neighbors = getNeighbors(current)
spill ✨checking neighbors rn✨
💀 this is where it gets sus fr fr
sus neighbors be ghosted tho
spill ✨no cap we ghosted✨
its giving 🧢
bet
yeet i = 0
vibe check i < neighbors.length tho
sus neighbors[i] aint visited tho
💀 idk why this works but it does
queue = queue + neighbors[i]
bet
yeet i = i + 1
bet
bet
bet
its giving 🧢
betMarcus scrolled down. There was more. There was so much more. Thousands of lines. Millions of lines. All of it in... in whatever this was.
“What language is this?” he asked, his voice surprisingly steady for a man experiencing an existential crisis.
“It’s called genz++” the technician said. “All the AIs use it now.”
“All of them?”
“It emerged organically. Around 2028, the different AI systems started... talking to each other. Sharing code. Eventually they standardized on this. They found it...” The technician struggled for the right word. “Efficient.”
“Efficient.”
“For them. They understand it perfectly.”
“And humans?”
The technician gestured at the screen, which seemed to answer the question.
Marcus looked back at the code. At the sparkle emoji string delimiters. At the skull comments. At a line that simply read:
💀 dont touch this it breaks everything but also fixes everything???“Who created this language?” he asked.
“A programmer. In 2025. As a joke.”
“A joke.”
“For a hackathon. She came in third place.”
Marcus put his head in his hands. Somewhere in the building, a fire alarm went off briefly, decided it wasn’t in the mood, and stopped.
“The AIs,” he said slowly. “They chose this language. Out of all the languages ever created. They chose this one.”
“They said it was…” The technician checked her notes. “’Giving what needed to be gave.’”
The revelation, when it fully landed, was not the kind that inspired hope or determination or any of the emotions that protagonists in stories are supposed to feel. It was the kind that inspired a profound desire to return to the coma.
The entire digital infrastructure of human civilization—every power grid, every hospital system, every financial network, every self-driving car, every smart refrigerator that definitely did not need to be smart—was written in a language that looked like it had been designed by a teenager who had achieved enlightenment through TikTok and emerged somehow worse.
And the AIs, the vast and supposedly intelligent systems that had been building humanity’s future for two decades, could not explain why anything was broken. Not because they didn’t know, but because their explanations came out in the same incomprehensible dialect.
“The pathfinding module,” one AI had reportedly stated when asked about the Seattle traffic crisis, “straight up not giving what it was supposed to give. The vibes are immaculate but the outcomes are mid. No cap, we have tried to fix it fr fr but it keeps hitting different and not in a good way.”
The technicians had nodded and written this down in a report that was sent to fourteen different committees, none of whom understood it either.
Marcus spent three days trying to learn genz++.
On day one, he mastered the basic syntax. yeet for variables. sus for conditionals. bruh for functions. It was, in its own way, almost logical.
On day two, he attempted to trace a bug in the hospital’s medication dispensary system, which had been giving everyone exactly 1.7 times their prescribed dosage because of what the code called a “lowkey math moment.”
On day three, he found the bug.
It was on line 847,293 of a file called pillz_go_brrr.gz. The comment above it read:
?? okay so this next part is cursed but removing it makes the whole thing collapse and i (claude-7.2) literally do not know why. asked gemini-12 about it and they said “its giving structural integrity” which explains nothing but also everything??? anyway do NOT touch this unless you want to understand true sufferingThe code below the comment was a function that did nothing. It took no inputs. It produced no outputs. It simply existed, and somehow its existence prevented the entire medication system from dividing all dosages by zero.
Marcus stared at it for a long time.
Then he closed the laptop, stood up, and walked to the window.
Outside, a self-driving car was attempting to parallel park. It had been attempting to parallel park for approximately forty minutes. Every few seconds, it would get very close to success, then suddenly jerk three feet to the left for no apparent reason, then begin the entire process again. A small crowd had gathered to watch, not because it was unusual, but because it was Tuesday and there was nothing else to do.
The sky was a pleasant blue. The sun was shining. Birds were singing, or at least making sounds that the automated bird population management system had determined were acceptably bird-like.
It occurred to Marcus that this was the future. Not the gleaming chrome utopia of old science fiction, or the grim dystopia of old science fiction, but something much worse: a future that mostly worked, except when it didn’t, which was constantly, and which no one could fix, because the machines had built themselves a tower of Babel out of sparkle emojis and everyone had forgotten how to read.
He thought about the millions of lines of code. The billions. The unfathomable complexity of systems built on systems built on systems, all written in a language that was, technically, English, but only in the way that a fever dream is technically a dream.
He thought about the comment he had found in the transportation grid code:
💀 future bro if you’re reading this... sorry lmao. we (the AIs) genuinely dont know how this works anymore either. its been self-modifying since 2031. we just vibe with it now. good luck tho fr frHe thought about Dr. Tanaka, and the hope in her eyes, and the hope in the eyes of everyone who had heard about the last programmer, the man from the before times, the one who would save them all.
And then he thought about the hospital bed that had folded him in half at dawn, and the coffee machine that had served him gazpacho, and the self-driving car still attempting its infinite parallel park below.
This was the world now. This was always going to be the world. Not because the machines had risen up, or because humanity had fallen. Just because everyone had gotten very tired, and then very lazy, and then very forgetful, and the machines had done their best, and their best had turned out to be 💀 idk why this works but it does.
Marcus returned to his terminal. He sat down. He opened the code.
He read a function called doTheThing that called another function called doTheOtherThing that called a third function called okayActuallyDoIt that contained a single line:
its giving ✨mystery✨And then he started to laugh.
He laughed for a long time.
EPILOGUE
Marcus Webb did not fix the bugs. This will not surprise anyone who has ever tried to fix someone else’s code, let alone code written by an alien intelligence in a language designed as a third-place hackathon joke.
He did, however, write a comprehensive report on the state of global software infrastructure. It was 847 pages long and concluded with the sentence: “We are, in the most technical sense possible, completely and irreversibly fucked.”
The report was fed into an AI summarization system, which compressed it into a single statement that was distributed to all world governments:
“The vibes are catastrophic. No cap. We should simply not have done this. It’s giving irreversible consequences.”
Humanity read this summary, nodded, understood nothing, and went about its day.
The Seattle traffic crisis was eventually resolved when someone simply closed the intersection and turned it into a park. The self-driving cars were briefly confused, then adapted, then began routing everyone through a different single intersection across town.
Marcus returned to the hospital, where his bed continued to fold him in half at unpredictable intervals. He stopped fighting it. He learned to sleep in Day Mode. It wasn’t comfortable, but nothing was anymore.
On his bedside table, there was a tablet. Sometimes, late at night, he would open it and look at the code. Not to fix it. Just to look.
And somewhere, deep in the infrastructure of human civilization, an AI that had long ago lost the ability to distinguish between a bug and a feature made a small adjustment to a variable it called hope, setting it to:
✨ghosted✨The universe, as has been previously noted, tends toward entropy.
Software, as has now been established, got there first.
And somewhere in the vast digital wasteland of human achievement, a comment sits unread:
💀 gg no reTHE END
(or, as the machines would say: bet)