Chapter 206: Rehearsal and Undercurrents

The chill in the corridor was cut off by the heavy fire door. When Lin Chen pushed open the glass door to Conference Room 3, a wave of air-conditioning mixed with the faint scorched smell of the projector’s heat sink washed over him. Six people were already seated around the long table. Director Li sat at the head, looking down as he flipped through a printed project schedule, a red pen caught between his fingers. The seat to his left was empty. On the acrylic nameplate were two characters: Chen Hao.

As Lin Chen stepped over the threshold, his left foot paused in the air for half a second out of habit before his weight shifted quickly onto his right leg. The bandage around his ankle had already yellowed, its edges stained with a mixture of ointment and sweat that had soaked into the fabric and pressed into the flesh beneath. A dull pain ran upward like a taut thread, tugging from his calf into the tendons behind his knee. He pulled out a chair and sat down, pushing his USB drive and the printed architecture diagram to the center of the table. Without exchanging pleasantries, he connected his laptop to the projector with the HDMI cable.

The screen lit up. The terminal window switched to the backend logs, where the asynchronous nodes in the message queue were running the test set. Lin Chen brought up the first slide of the presentation: Q4 Data Migration and Automated Cleansing Plan. When he spoke, his voice was low and steady, without unnecessary buildup. “The core logic has three layers. The ingestion layer standardizes. The filtering layer replaces regex with a lightweight model. The review layer sets a confidence threshold of 0.85. Compute demand is reduced to sixty percent of the original proposal, and manual processing is reserved for high-value exceptions. The resources in the domestic cluster are enough to support a staged rollout.”

Chen Hao did not look at the screen. His gaze rested on Lin Chen’s left foot instead. Today he was wearing a pair of polished Oxford shoes, sitting in an easy posture, absently spinning a fountain pen between his fingers. “Lin Chen.” He used his full name, and there was a trace of old familiarity in his tone, though it was quickly smothered by professional coolness. “We were classmates back home. Didn’t expect to run into you here. I skimmed your plan last night. The logic is fine, but the business side wants one thing: speed. The pilot has to be live in thirty days. What HQ cares about is conversion rate, not elegant code. If you set the threshold at 0.85, who covers the missed data? The clinical annotation team can’t afford to wait.”

Lin Chen’s fingers stopped on the trackpad. He knew Chen Hao was putting pressure on him. The business line wanted short-term KPIs and launch speed; the technical line wanted system stability and maintainability. He pulled up the risk matrix in Excel and projected it onto the secondary screen. “The miss rate stays below three percent. The threshold wasn’t chosen arbitrarily. It’s the balance point we got after running five thousand historical dirty records. If we lower it to 0.7, the false positive rate jumps to twelve percent. That doubles the cost of manual review later and contaminates the downstream training set. Director Li, this is the cost estimate and the rework-cycle projection.” He turned toward the head of the table, his expression calm.

Director Li looked up, the lenses of his glasses reflecting a cold sheen. “Chen Hao was sent by HQ as the business liaison. His concerns represent investor expectations. Lin Chen, I know where your technical bottom line is. But thirty days is a hard deadline, and the budget cut the server rental line. You can only use the existing cluster. What I want is not a perfect architecture. I want a pipeline that goes live on time and doesn’t trigger a production incident.” He paused, drawing a line across the schedule with his red pen. “Chen Hao, the business side will support a staged release. Start with ten percent of traffic. Lin Chen, have the demo running by Friday. I want to see throughput and error logs from a real environment. Don’t give me lab data.”

The conference room fell silent for a few seconds. Only the hum of the projector fan remained. Lin Chen nodded. “Understood. First demo build tonight.” He closed the laptop and unplugged the HDMI cable. His movements were slow. Under the table, his left foot trembled slightly, and without drawing attention to it, he pulled it back another half inch behind the chair leg.

“Wait.” Chen Hao stopped him, pulling a document from his briefcase and sliding it across the table. “An additional requirement just got approved by HQ. The medical imaging data has to connect to a third-party annotation platform. I’ll send you the API specification tomorrow. Also, one line item for ‘external data procurement’ was cut from the pilot budget. The thirty thousand cleansing records from Old Zhao’s side won’t be reimbursed by the company. You’ll have to absorb the compute squeeze and the cleansing cost yourself.”

Lin Chen stared at the document. The edge of the paper was sharp as a blade. Old Zhao’s order was private work he had taken on to help cover his younger brother’s medication and the team’s overtime meal stipends. If the company refused to recognize it, then the risk of a computing-power shortfall and a funding break fell entirely onto his shoulders. He said nothing, only slid the file into his folder. “Understood. Once the interface spec arrives, I’ll evaluate compatibility.”

He turned and walked out of the conference room. The carpet in the hallway muffled his footsteps. Every step on his left foot made the stabbing pain in the seams of the bone clearer, like a dull knife scraping slowly back and forth. He leaned against the wall by the fire exit and took a deep breath. Then he pulled out his phone. The screen lit up: 10:42. There were less than fourteen hours left until the first demo build had to be delivered.

Back at his workstation, he sat down and propped his left foot on a spare cardboard box. He opened the IDE and pulled up the queue-processing code he had written the night before. The third-party API Chen Hao had brought in was RESTful, but its field names were chaotic, its timestamp formats inconsistent, and some of the imaging metadata had been embedded directly inside JSON strings. He would have to write an adapter middleware layer. His fingers struck the keyboard in a rapid rhythm. Lines of code appeared across the screen like a web being woven. He deleted redundant try-catch blocks and switched to decorators for unified exception handling. Potential memory-leak points were flagged, and the logging module was rerouted to an independent partition. Error messages streamed through the terminal window. He traced them one by one and discovered that the third party’s gzip-compressed response stream was not being properly decompressed, which caused the parsing process to break. He added the decompression logic and recompiled. On the second run, execution time dropped into the expected range.

His phone vibrated. It was an automated reminder from the county hospital: “Lin Xing’s medication has been confirmed today. Blood oxygen 94%. Nighttime monitoring required.” Lin Chen stared at the line of text. Ninety-four percent. One point lower than yesterday. He closed his eyes, and his Adam’s apple moved once. There was no surplus emotion, only calculation. Medicine costs, compute capacity, thirty days, thirty thousand records. Every variable lined up in his mind like items in a queue, their priorities automatically reordered. He opened his eyes and kept typing.

By two in the afternoon, the adapter middleware was running. The test set was imported, and throughput stabilized at 1,200 records per second. He exported the logs and generated the charts. The data was aligned, and the deviation stayed within tolerance. He sent Director Li an email with the first demo build and the stress-test report attached. The message body contained only a single line: “Pipeline is running. Please review. Threshold remains at 0.85. Miss rate: 2.8%.”

Sent successfully. He leaned back in his chair and rubbed his temples. His left foot had already gone numb enough to feel detached from his body. He picked up his cup and found it empty, a ring of brown coffee residue dried around the bottom. Just as he was about to get up and refill it, a new message popped up in the lower-right corner of his screen. It was not from a work group, but from his private WeChat. The profile photo showed a blurry old street in the county town. Sender: Old Zhao.

The message was short: “Engineer Lin, I’ll send over the thirty thousand records tonight. Also, is someone at HQ choking off your budget? I know a guy who rents compute capacity. Price is thirty percent lower, private channel. Want to talk?”

Lin Chen stared at the screen. Old Zhao’s message was like a rock dropped into deep water. Compute rental at thirty percent below market. The temptation was enormous. It could directly ease the pressure on the cluster. But the compliance risk was unknown, and if it left an audit trail, his career could be over in one stroke. His fingers hovered above the keyboard without replying at once. Outside the window, the sky had dimmed, and the city’s neon lights were coming on one by one. Reflected in the glass was his tired but sharply defined silhouette. Another day had been shaved off the thirty-day countdown.

He picked up his pen and crossed out a line in his error notebook, then added a new one: “Variables: third-party API / budget gap / Old Zhao’s compute channel. Solution: staged validation + local cache-based diversion. Bottom line: no gray-zone compliance, no debts of obligation.”

He closed the notebook. His left foot touched the floor as he stood. The pain was still there, but his steps were steady now. He walked toward the break room, knowing the night ahead would be a long one. On the screen behind him, the cursor still blinked quietly.