Cherreads

Modern Coder King

moonpaper
49
chs / week
The average realized release rate over the past 30 days is 49 chs / week.
--
NOT RATINGS
984
Views
Synopsis
When a mysterious system awakens inside 24-year-old programmer, it doesn't give him superpowers, and it makes him better at the one thing that already runs the world. Better at seeing code, better at breaking it, and better, at eventually, at rewriting it altogether. Root Access is a long-form progression fantasy for readers who want the power fantasy dialed up — and the tech grounded in something real. Every victory traces back to a concept: reverse engineering, exploit chaining, distributed control, emergent AI, systems architecture. The power is real because the knowledge is real. And it only gets more dangerous as it scales. From overnight hacking legend to covert contractor to the single most strategically dangerous person alive, Kai's rise isn't a shortcut. It's a war of escalation — one upgrade, one enemy, one rewritten system at a time.
VIEW MORE

Chapter 1 - Chapter 1 — Dead Weight

The error message had been sitting on Marcus Vane's screen for eleven minutes.

Not because he didn't know the answer. He'd known the answer in the first thirty seconds. The problem was a race condition buried inside a poorly threaded socket handler — the kind of bug that junior developers introduced when they copied async patterns from Stack Overflow without understanding what "non-blocking" actually meant. Three lines of code. Fix the mutex lock, restructure the callback chain, add a guard condition. Done.

The problem was that fixing it would take eleven seconds, and he had already been paid for eleven minutes.

Marcus leaned back in his chair and let his eyes drift to the ceiling of the server room. The fluorescent light above his workstation buzzed at a frequency that no one else in the building seemed to notice. He had complained once, eight months ago, when he'd first taken the contract at Helix Data Solutions. The facilities manager had nodded, smiled, and done nothing. Marcus had stopped complaining. The buzzing was still there. It had become a kind of white noise now, something he associated with this job the way other people associated certain songs with certain memories — not pleasant, but familiar.

He was the best programmer in this building. He had known that on day two. By day five he had known he was probably the best programmer in a four-block radius. This was not arrogance. It was pattern recognition. Marcus had been watching the other engineers for eight months and he understood their limits the way a chess player understood a novice's opening — not contempt, just clarity.

Dara Huang was competent, methodical, would be excellent in five years if she kept her head down and her curiosity intact.

Phil Ostergaard was fast but sloppy, produced code that worked right up until someone looked at it sideways.

Their team lead, Gordon Fitch, had stopped actually writing code sometime around 2017 and now survived on meetings and vocabulary.

Marcus typed the three-line fix. Committed. Pushed.

His phone buzzed.

He glanced at it. A text from his sister, Nadia.

*hey. mom fell again. she's okay but you should know.*

He read it twice. Set the phone face-down on the desk. Looked at the ceiling.

Their mother was fifty-eight years old and her knees had been failing for four years. The right one was bone-on-bone now. The surgery she needed cost thirty-one thousand dollars with her current insurance gap. Marcus had done the math six times, from six different angles, looking for some arrangement of his freelance income, his contract salary, and Nadia's part-time nursing income that added up to thirty-one thousand in any reasonable timeframe. He had not found one.

He turned his phone face-up and typed back: *I know. I'll call tonight.*

Then he opened a new terminal window and pulled up his personal side project — the thing he worked on in the gaps between tasks when no one was watching — a lightweight distributed crawler he had been building for three months to scrape public procurement databases for patterns in government contract awards. Not because he had any immediate use for it. Because the problem was interesting, and interesting problems were the only thing that made the buzzing light bearable.

He was forty minutes into a refactor of the crawler's indexing logic when the migraine started.

---

It was not a normal migraine.

Marcus had migraines occasionally — always had, since his early twenties. They came with the usual warning signs: a shimmer at the edge of vision, a slight sensitivity to sound, a feeling like the air pressure in the room had changed. Then the pain, which he managed with medication and darkness and a few hours of miserable stillness.

This was different.

The shimmer started the same way, at the left periphery, a soft distortion like heat rising from asphalt. But it didn't spread. It contracted. It pulled inward, narrowing to a single point just off-center in his left eye, and then the point went very, very bright — and Marcus had just enough time to think *this is not a migraine* before everything went white.

No pain.

The white lasted approximately two seconds. Then it resolved into his normal field of vision, the server room, the buzzing light, the terminal window with his crawler code half-finished on the screen.

But something had changed.

He looked at the code.

It was the same code he had written. The same variables, the same function names, the same architectural decisions he'd made at 9 AM this morning. But looking at it now felt like looking at a familiar room after someone had turned on a light he hadn't known was off. The structure was suddenly *obvious* in a way he didn't have a word for. Not just readable — *transparent*. He could see the logic of it the way you could see the frame of a building when the walls were made of glass.

And he could see the flaws. Not individual bugs. The underlying *geometry* of the flaws — the places where his decisions had been locally reasonable but globally suboptimal, the trade-offs he'd made casually that were, he now understood, more expensive than he'd realized.

He started rewriting.

He wrote for ninety minutes without stopping, without looking up, without reaching for his coffee. When he finally stopped and read what he had produced, the crawler's indexing logic was not merely fixed. It was architecturally different. Cleaner in a way that took him a moment to fully articulate even to himself — like someone had removed a load-bearing wall and replaced it with something stronger that took up half the space.

He sat back. Blinked. His eyes ached slightly, the way they did after a long reading session.

His phone buzzed again. A calendar reminder for his 3:00 PM sync with Gordon Fitch.

Marcus looked at the code. Looked at the phone. Looked at the code.

*What just happened?*

He didn't have an answer. He filed the question away in the part of his mind reserved for anomalies that didn't yet have enough data to resolve, and he went to his meeting.

---

Gordon Fitch ran his team syncs like a man who had watched too many TED Talks about leadership and absorbed only the aesthetic. He stood. He used a whiteboard. He said things like "velocity" and "ownership" in ways that had been drained of all specific meaning.

Marcus sat in the back and said nothing. He had learned that saying nothing in these meetings preserved his energy for things that mattered.

"Marcus." Gordon pointed at him with a dry-erase marker. "The socket bug?"

"Fixed and deployed. Eleven forty-seven AM."

"Good." Gordon made a mark on the whiteboard that represented nothing. "Any blockers going into the sprint?"

"No."

"Great. Great." Gordon moved on to Phil, who had many blockers, all of which were other people's fault.

Marcus looked out the small rectangular window on the far wall of the conference room. The afternoon light was doing something specific to the parking lot below, turning the asphalt a warm gray, making the white parking lines look slightly phosphorescent. He noticed this the way he had been noticing things all afternoon — with a precision that was new. A granularity.

It was like his perception had been running at a lower resolution than it was capable of, and now someone had bumped up the settings.

He pressed two fingers to his left temple and held them there for a moment. No headache. No pain.

Just this new, exact, unsettling clarity.

---

He called Nadia at 7:30 that evening, walking from the metro stop toward his apartment building. The night was cold and still, the kind of early spring cold that felt like the season was still making up its mind.

"She won't go back to the doctor," Nadia said. She had the voice of a person reporting a fact they had already accepted, which was a register Marcus associated with his sister's exhaustion. She spent a lot of time there.

"I know."

"She says the cortisone helped. It didn't help, Marcus. I watched her get up from the couch today and she—" A pause. "She has a certain way she holds her face when it hurts and she doesn't want you to know. You know the face."

"Yeah."

"She needs the surgery."

"I know she needs the surgery."

"Then—"

"I'm working on it, Nad."

There was a silence on the line. Not hostile — his sister had never been hostile, even when she had every right to be. Just tired.

"Okay," she said. "Okay. Call her tomorrow, she'd like that."

"I will."

He hung up and stood outside his apartment building for a moment, looking at nothing in particular. Thirty-one thousand dollars. He turned the number over in his mind the way he turned problems over — looking for the angle he hadn't found yet.

His laptop was in his bag. The crawler was running on his home server, quietly indexing.

He had the new clarity.

He went inside.