← back to the book
The Silence of the Code

The night COBOL didn’t break

chapter 1 of 3 · 5 Nov 2026

The screen did nothing, and it did so with such dignity that Markos Andreou, thirty-four, holder of four certifications and an entirely unjustified sense of self-worth, felt for the first time that a piece of furniture was staring back at him.

It was two-ten in the morning, November, and outside it was raining with the thin, persistent politeness of a creditor. The observation chamber had four workstations, green letters on a black screen: the green some engineer in the eighties had decided would calm operators, never imagining that one day someone would sit before it who only calmed down when something broke.

And Markos broke things. The institute paid him for that: to push its systems to the edge of the table and measure how quickly they shattered. He was good. He was, as he himself put it, the best to ever pass through that building, and no one had found a way to contradict him without losing the argument.

In the profession’s slang, to “break” a program meant to force it to do what it shouldn’t: feed it data it didn’t expect, ask it to do two things that couldn’t coexist, push it until it crashed, that is, until it stopped abruptly and confessed where its weakness lay. The institute paid Markos to find them first, before someone who wouldn’t file a report did.

Two days earlier, in the foyer, he had bet with Giorgos Stavrou, the sysadmin¹ who had worked in the building since computers took over keeping track of some rich people’s money, and later, everyone’s.

“COBOL is archaeology,” Markos had said. “And archaeology shatters at the first attempt.”

Giorgos had shrugged, the look of a man watching a wave crash against a pier. “It holds. Not because it’s some new, cutting-edge technology, but because it just exists. Like a pier. Seems dull, but it’s there and it does its job. And dull things never die, because they do their job efficiently, no matter how many years go by.”

The stakes: whoever lost wouldn’t get to choose dinner for the rest of the week. Markos had already lost, and every second the screen stayed still added interest to his debt.


COBOL, for those who don’t give it the respect it deserves, is a language written by committee in 1959ᵃ: six people and a Pentagon that wanted a common language for all its machines. It was a committee that had decided poetry was overrated and that sentences should end with a full stop, like a tax return. One of the six, exasperated by the slow pace of the work, bought a tombstone with the word COBOL engraved on it for fifteen dollars and sent it to the Pentagonᵇ. In 1975, Dijkstra wrote that using it mutilates the mindᶜ. The language didn’t die from either.

A language emerged that reads like a contract, and because it reads like a contract, no one dared touch it. It’s estimated that some two hundred twenty billion lines of it are still running, processing pensions, payrolls, insurance claims, and three trillion dollars a dayᵈ. In 2000, the world spent hundreds of billions to save it from a single digit of the year, then lived through Y2Kᵉ as a reprieve, not a warning. In 2020, a governor in New Jersey, USA,ᶠ went on television and asked for volunteers who knew COBOL, because those who did were old, and the state had nowhere else to turn. That’s when the world realized, decades too late, that its civilization rested on something no one knew how to operate anymore.

Markos had read the news and laughed. He was one of those who grew up with Python and Go, and saw COBOL the way you see an animal in a cage: with curiosity, and the faint certainty that the cage was there for a reason.

Tonight he was testing SETL-09, a settlement routine². Settlement is what happens every night after everyone has paid for everything. When you pay for a coffee with a card, the money doesn’t go anywhere at that moment. Promises are exchanged: your bank promises the café’s bank. At night, someone has to gather all the day’s promises, millions of them, reconcile them, and record who owes what to whom. A routine with no glory and no rival, like the newbie clerk stamping papers at the last counter.

Markos sent it a request packed with everything he knew to make a system forget what it was.

The request went in. And didn’t come out.

There was no crash. A crash is honest: a program that breaks tells you it’s hit a wall. There was no timeout³, no warning, no line in the log⁴. The routine behaved like a clerk at a counter who doesn’t say no, just doesn’t lift their head.

He tried again. Three times, five, six. Six times the request vanished into the same polite silence. On the seventh, the routine answered immediately, clearly, without a trace of guilt, like someone doing you a favor so you won’t suspect they’re bothered.

Markos looked at the seven lines in a row and felt something he’d never felt before in front of a system: that he was one of the two who hadn’t decided who was watching whom.


Giorgos Stavrou walked in at twenty to three with two machine coffees that tasted of burnt rubber, charged to the expense account. He was sixty-eight, square and grey like the building itself, where he had worked for thirty-five years, long enough for the doors to open if he stared at them. He was the mainframe⁵ keeper: the only one who went down to the eighteen-degree room, behind doors that only opened with a card Markos didn’t have.

“Am I winning?” he asked, and set one coffee on the keyboard.

“The screen didn’t break,” Markos said. “That doesn’t mean you’re winning.”

“Fair enough.”

“Something’s holding. The SETL-09. It takes the request and doesn’t return it. No error, no log. Then, one in seven times, it responds normally.”

Giorgos took a sip and didn’t react. “The scheduler⁶ checks the batch⁷, not the routines. If the batch comes back, everything’s green.”

“Meaning no one monitors the routine.”

“It’s like the ocean floor,” Giorgos said. “You know it’s there.”

Markos opened the audit trail⁸ of the six requests that had been held. He didn’t expect anything. But each of the six ended with the same signature, eight letters, like handwriting in the margin:

OPERATOR: GIBARIAN

The seventh was missing him.

“Who is GIBARIAN?”

Giorgos looked at the screen for a moment. He was the kind of man who knew ghosts didn’t exist, just as one knows a house always has a sound that can’t be explained. “Old account. Never appeared on any list. No one ever saw him working, only signing. Left before I got here.”

“And why is he signing tonight?”

“An account doesn’t sign,” Giorgos said. “A program signs.”

He said something else: he took a small spiral notebook from his pocket, yellowed from use, and placed it on the desk, open. Pages filled with lines, side by side, groups of five with a diagonal slash, like days in prison.

“Forty-one times since June,” he said. “There’s no field for that. The scheduler wouldn’t log it. I wrote it down myself.”

“Did you tell anyone?”

“I told management.” Giorgos looked at his coffee. “They said thank you.”


Anna Leonti’s office was on the top floor, where the morning light slants in through the tall windows and falls on a glass table, empty except for a laptop, a glass of water, and a phone face down. She was forty-five and had the face of someone who had signed many papers without reading them, not out of carelessness, but necessity, like a castaway grabbing whatever floats.

“Mr. Andreou. Two sentences. What did you find?”

Markos had prepared for five minutes. She gave him two. “A settlement routine stops responding at intervals. It doesn’t throw an error or write a log, and the monitoring system shows it as complete.”

He didn’t tell her about GIBARIAN, or about the notebook. The discovery was his, and Markos never shared discoveries before he understood what they were worth.

Anna didn’t raise an eyebrow. She hadn’t asked what “routine” meant. “Your report will be read by people who only know how to read one word: danger. They won’t ask what a routine is. They’ll sell it.”

“So you want me to bury it.”

“I want you to write what you can prove. Can you prove an attack surface?”

Markos wanted to say yes. He was so close to yes he could taste it, metallic in his mouth. “No.”

“Then it’s not part of your job.”

“I can’t explain what I found.”

“Exactly,” Anna said.

In the half-second that followed, she turned her phone screen-up, glanced at something, and turned it back. Markos, who only ever saw what others saw without noticing, understood that someone on the other end of the screen was waiting for an answer. And that Anna wasn’t the first to be asked.

“The upgrade starts Monday,” she said. “We have one chance to get it right. Don’t ruin it for me with something you can’t explain.”

There was no threat in her voice. Worse: there was a plea, dressed in a suit.


That evening he wrote the report in the green-lit chamber, the light flowing over the keys like water in a channel. He wrote about access rights, encryption, data integrity, every door he had pushed that had not opened. He also wrote a sentence that was true in the way shadows are true: “No exploitable attack surface was identified.”

It was correct. And it was the most dishonest thing he had ever written. There are truths that lie with surgical precision, and Markos had just performed his first operation.

At eleven fifty his system access had ten minutes left. The building was empty. Below, only the guards and the night operator would remain, and, two floors down, behind the card-locked door, Giorgos.

Since the afternoon, the upgrade logging tool had been running through the routines one by one, compiling the transition inventory. Markos had seen it in the process list and ignored it, the way you ignore a refrigerator’s hum.

Markos had not intended to do it. His body was faster than his decision. He sent one last request to SETL-09.

The routine answered at once. Cleanly. Without knowing it, Markos smiled: as if someone had thanked him for something he had not done.

Then he saw the second line.

The SETL-14, another settlement routine with a different number: he had never touched it. No human had ever touched it. And yet, before his eyes, without any human request, it stopped. It didn’t crash, didn’t notify. It simply ceased to move, like water ceases to move before something.

He opened its audit trail. The first entry was from the same moment, eleven fifty-six: an automated read by the modernization tool, which had passed through that routine as well. The second was the signature:

OPERATOR: GIBARIAN

He bent to copy it down. On the screen’s clock, the digits turned to zero. The system logged him out on its own, with the politeness of a doorman closing a door, and his permissions ceased to exist before he could finish the word.

Two floors below, in the eighteen-degree room, Giorgos Stavrou opened his notebook and drew a line. Then, after thinking about it, he drew a second one, in a different column.

Outside, the rain kept owing everyone.


Explanations of terms

1. Sysadmin

A sysadmin (system administrator) is the person who keeps an organisation’s machines alive: they set them up, monitor them, fix them when they break, and know where every cable ends up. In large institutions, they’re usually the only one who remembers why something was done twenty years ago.

2. Routine

A routine is a small piece of a program that does one specific job and nothing else: it calculates, transfers, checks. A large program resembles a factory full of routines, each in its own machine, each waiting for another to call it.

3. Timeout

A timeout is the rule that a program doesn’t wait forever. If it doesn’t get a response within a set time, it stops and declares that something went wrong. It’s an honest way to fail, because everyone sees that time ran out. In the story, SETL-09 doesn’t even do that.

4. Log

A log is a program’s diary. Every time something happens (the program starts, stops, fails, or someone makes a request), it writes a line to a file, along with the time. When something goes wrong, technicians open the log to figure out what happened. A program that writes nothing to its log while something is happening is like a witness who refuses to testify.

5. Mainframe

A mainframe is the central computer of a large organisation: a massive machine, kept in a refrigerated room, running non-stop the jobs that must never stop, like payments and accounts. It doesn’t look like a desktop computer, but everything else depends on it. That’s where COBOL runs.

6. Scheduler

A scheduler is the program that decides which job will run, when, and in what order, like a factory manager waking the machines by the clock. It doesn’t check how each machine worked, only whether the shift is over. If everything looks green, it moves on to the next job.

7. Batch

A batch is a bundle of tasks that run together, usually at night, with no one sitting in front of the screen. A single batch can contain hundreds of routines, like SETL-09. The system checks whether the whole batch completed, not what each one did.

8. Audit trail

An audit trail is stricter than a log. It records who did what, when, and under which account. The OPERATOR field shows which account or program performed each action. It exists for auditors and courts, and it must never be deleted. If the log is the program’s diary, the audit trail is the sign-in book at the building’s entrance.


Historical notes

a. The 1959 committee

In May 1959, the US Department of Defense convened a meeting of around forty people at the Pentagon, including representatives from government agencies, computer manufacturers, and major users. The goal was a common programming language for business applications: one that read almost like English and ran on machines from different companies. The work was assigned to a smaller subcommittee of six people from IBM, RCA, and Sylvania. The name COBOL stands for Common Business Oriented Language.

b. The tombstone

Howard Bromberg, RCA’s representative on the committee, exasperated by its sluggishness, bought a tombstone inscribed with the word COBOL for fifteen dollars and sent it to Charles Phillips, the committee’s chair at the Pentagon. He denied it for years. He admitted it in 1985, on the language’s twenty-fifth anniversary, and the tombstone is now kept at the Computer History Museum in the US.

c. Dijkstra

Edsger Dijkstra (1930–2002) was a Dutch computer scientist and one of the most influential voices in the field. In a 1975 essay, he wrote that using COBOL cripples the mind and that teaching it should be considered a criminal offence. It was an exaggeration from a man who enjoyed provocation, and the language outlived him.

d. The numbers

The figures mentioned (two hundred and twenty billion lines, three trillion dollars a day) are estimates circulating in studies and publications. There is no official counter, because no one has tallied all the COBOL still running. The Computer History Museum already reported over two hundred billion lines by 1997.

e. Y2K

Many old programs stored the year with two digits (98 instead of 1998) to save space. At the turn of the millennium, the risk was that they would read 00 as 1900. The world spent years and, by some estimates, hundreds of billions of dollars fixing the code. Because the fix worked and nothing dramatic happened, many concluded the danger had been overblown.

f. New Jersey, 2020

In April 2020, at the start of the pandemic, unemployment benefit claims surged, and the systems of the US state of New Jersey, written in COBOL decades earlier, struggled to keep up. Governor Phil Murphy publicly called for volunteers who knew the language. Similar appeals followed in other states.