Chapter Three: The Code
Lucas’s voice came out louder than he intended, which was because his heart was doing something complicated and he was managing the adrenaline of finding an unexpected person at his desk in his home office at two in the morning touching the machine that contained everything.
Emma spun away from the keyboard so fast she nearly took the chair with her.
She was young — mid-twenties at most — with her hair pulled back for work and a cleaning company lanyard still around her neck and an expression of pure alarm that communicated, very clearly, that she was not a threat. She pressed back against the desk, her hands up slightly, instinctively, and said: “I’m sorry — I just — there was something that looked incorrect — I only wanted to —”
“You were typing,” Lucas said.
“Yes.”
“In my code.”
“Yes.” She said it plainly, without trying to minimize it, which was either bravery or the honest practicality of someone who has decided there is no point in minimizing the obvious. “I saw something that didn’t look right. I’m sorry. I shouldn’t have —”
Lucas crossed the room, already composing the rest of the conversation in his head — the call to the agency in the morning, the security review of the machine, the process failure that had allowed this —
He looked at the screen.
He stopped.
He leaned in slightly, the way you lean in when you don’t trust your eyes, when you want the distance between yourself and the thing you’re seeing to be smaller so the thing will make more sense.
The section of code currently on the screen was the authentication handler. Lucas knew this section the way he knew the floor plan of his own house — he had reviewed it personally, twice, he had walked Marcus from the Berlin firm through it line by line, he had read the ex-Google engineer’s notes on it three times. He knew it was not the problem. His team had ruled it out in week two and he had agreed with their reasoning.
Except.
What was on the screen now was different from what he remembered. Not dramatically — the architecture was the same, the logic was the same. But something had changed in the threading model, in the way concurrent requests were being queued before hitting the payment processor handshake, and the change was so clean and so sensible that it took him a moment to understand why it hadn’t been there before.
Because no one had seen it.
He pulled the chair back to the desk. He sat down, forgetting entirely that he had been about to say something else, and he read. Carefully, from the top of the function, tracking the logic the way you track a river from source to sea. He ran it mentally against the load condition scenarios that had been failing the benchmarks. He ran it again.
It worked.
Not just worked — was better. The fix was elegant in the specific way that good engineering is elegant, where the solution looks obvious only after someone has found it, where you wonder afterward why no one saw it sooner and the answer is that you need a particular kind of eye for this type of problem and apparently none of the people he had been paying did.
He turned from the screen.
Emma was still standing against the far wall, lanyard around her neck, hands no longer raised but held carefully at her sides, watching him with the expression of someone awaiting a verdict.
“How long did it take you?” he asked.
She blinked. This was not the question she had been waiting for. “To find it?”
“To find it and fix it.”
She thought about it honestly, which he appreciated. “Finding it — maybe two minutes after I actually looked at it. I was looking for maybe a minute and a half before that.” She paused. “Fixing it took longer. Maybe twenty minutes? I kept checking the handshake behavior because I wanted to make sure I wasn’t introducing something in the threading that would cause a different problem downstream.”
Lucas looked at her. He looked at the screen. He looked at her again.
“Sit down,” he said.
“I should really —”
“Please,” he said. “Sit down. I’m not — I’m not going to report anything to the agency. Sit down.”
She sat, carefully, in one of the two chairs on the other side of the desk — not the one she’d been working in, the visitor’s chair, which said something about her reading of the room that he noted.
“What’s your name?”
“Emma Reyes.”
“Emma. How do you know this code?”
“I don’t know this code,” she said carefully. “I know the language, and I know the kind of problem this is. The authentication threading issue with a rate-limited external processor — it’s a known failure mode, there’s a paper from a team at Carnegie Mellon from 2019 that covers the category. Once I saw the structure I knew what to look for.” She said it without pride, just accurately. “I wasn’t sure my fix was right. I was going to leave a note.”
“A note.”
“I was going to write down what I’d done and leave it on the desk,” she said. “So whoever looked at it in the morning could check my work and decide whether it made sense. I wasn’t going to — I wasn’t trying to —” She stopped. “I know it wasn’t my place to touch it. I’m sorry for that part.”
“You were going to leave a note,” Lucas said slowly, “explaining a fix to a problem that six professional engineers and two senior consultants couldn’t identify in six weeks. An unsigned note. On the desk.”
“I didn’t know it had been a problem for six weeks,” she said. “I just saw that something was off.”
He was quiet for a moment.
“You were studying computer science,” he said. It wasn’t entirely a question.
“Two years,” she said. “At State. I had to — there were things I needed to take care of. I left.” She said it without self-pity, in the tone of someone who has made peace with the accounting of their life, which did not mean they found the accounting pleasant. “I’ve kept reading. It costs nothing to keep reading.”
Lucas looked at the screen once more. The fix sat there, clean and correct and already running in his mind against every scenario, passing all of them.
“Do you want to walk me through your reasoning?” he asked. “Not because I doubt it. I want to understand how you got there.”
She looked at him for a moment, checking the question for angles, and then apparently deciding it was straight. She moved her chair around to his side of the desk. She pointed at the screen.
“Here,” she said. “This is where the request queue was building.”
They were there until four-thirty in the morning.
