Chapter 213: Boundaries and Measures

5:40 a.m. The monitor in the hospital room emitted a low, steady beep, like some slow metronome. Lin Chen opened his eyes, and a dull ache pulsed through his left ankle, needling deep into the seams of the bone. He did not get up at once. First he took three deep breaths, and only after confirming that his heartbeat was steady did he slowly pull back the blanket. A laptop lay open on the folding table by the bed, its screen still frozen on last night's IDE. The cursor blinked with mechanical regularity on the line beneath class DataCleanerV3:.

Bracing himself against the bedrail, he stood up, putting his full weight on his right foot while his left merely touched the floor. He went to the bathroom and splashed cold water on his face. In the mirror, the man staring back at him had hollowed eyes and a jawline drawn tight as wire. When he returned to the bedside, he opened the drawer and took out the boxes of sodium valproate and levetiracetam. He checked the dosage, poured some water, then glanced at Xiaoman, who frowned faintly in his sleep. Lin Chen crushed the tablets into warm water and used a cotton swab to moisten his little brother's lips bit by bit. Xiaoman did not wake; only a vague swallowing sound came from his throat. Lin Chen put the empty medicine box into a sealed bag, opened the ledger he carried with him, and wrote: First day on the new medication; out-of-pocket portion deducted. Balance: 2140.50. The figures came out lightly, the pen never pausing.

At exactly seven o'clock, he connected to the hospital corridor's public Wi-Fi. The signal was weak; web pages loaded sluggishly. He opened his email and sent the message he had drafted the night before. Subject: Regarding Request for Transfer to Remote Support Team and Work Handover. The body contained no emotion, only a list: current project progress, repository access transfer milestones, future support response times, and the conditions for initiating the resignation process. He copied Director Li, the HRBP, and the department assistant. Sent successfully. He closed the laptop and leaned against the wall. Gray-white morning light filtered in through the window at the end of the corridor, and the air smelled of disinfectant mixed with old bedding.

Ten minutes later, his phone vibrated. Director Li.

“I've read your email.” Director Li's voice was flat. “I'll give you two weeks for the handover. The performance wager agreement is void, but your compensation will be settled based on actual output. The remote support team doesn't have any headcount available right now. You can take work as an external consultant first and be paid per assignment. The company doesn't keep idle people, and it doesn't stop those who want to leave.”

“Understood,” Lin Chen said. “I'll send you the handover documents before the end of the workday. As for the consulting contract, I'll cooperate with Legal through the proper process.”

“Don't make your road narrower than it has to be.” Director Li paused. “Layoffs are happening everywhere right now. If you go out on your own at a time like this, your social insurance contributions get interrupted—who's going to pay your mortgage?”

“I have a plan.” Lin Chen's voice remained calm. “Thank you for looking after me these past few years, Director Li.”

The call ended. No attempt to keep him, no threat either. In the adult workplace, the rules were clear and the lines sharply drawn. He let out a breath—not relief, exactly, but the acknowledgment that his retreat was gone and only forward remained. He could not stake his life on someone else's scheduling sheet, nor could he let the family's ledger be held hostage by the company's KPIs. Linear income could not fill a hole being eaten open at an exponential rate. That was a math problem, not an emotional one.

At 8:30, he went back into the room and settled the laptop on his knees. The core of V3.0 was decoupling. He extracted the hard-coded regular expressions and turned them into an independent rules.yaml configuration file. He added a retry mechanism and breakpoint resume to the exception-handling module. The logging module now output by timestamp and error level to make later tracing easier. His left foot began to go numb, so he shifted position, propped it on a pillow, and kept typing with his right hand. Lines of code accumulated on the screen one after another, like patches being hammered onto a leaking ship. He had to push the fault tolerance above 99.5 percent. Otherwise, any single interruption would devour what little strength he had left.

At eleven o'clock, Old Zhao sent over a compressed file. “Dictionary and raw data. Over three hundred fields, some with nested JSON. I want the results by three p.m. Friday. Don't keep me waiting.”

Lin Chen extracted it. The file structure was more complicated than he had expected. The main table was CSV, but the related tables were in Excel, and the nested fields were mixed with full-width and half-width symbols plus invisible characters. He wrote a pre-parsing script and ran a sample batch. Error: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 10: invalid start byte. Not an encoding issue—the file header had been tampered with and mixed with compression markers. He rubbed between his brows, rolled the script back to the previous version, and rewrote a binary sniffing module. First determine the file type, then dispatch the proper parser. There were no shortcuts in technical work. You could only peel back the shell of dirty data layer by layer.

At two in the afternoon, the script successfully processed the first batch. Cleaning rate: 87.3 percent, below the expected 95. He checked the logs and found the problem: the timestamp formats inside the nested JSON were inconsistent. Some had time zones, some did not, and some were simply the string “unknown.” He could not force-convert them; that would lose data. So he added a conditional branch in rules.yaml: if format == 'unknown': log.warning('skip'); else: parse(). At the same time, he added a note to the delivery documentation: “Records with missing timestamp fields or abnormal formats have been marked as NULL and exported separately. They are not counted among the valid cleaned records. If completion is required, original business-system logs must be provided.”

That was the bottom line. He could not do the client's data governance for them; he could only do data cleaning. Only when the boundary was made clear could responsibility be made to land where it belonged. Leaning back in his chair, he closed his eyes. What filled his head was not code, but the ledger. The twelve-thousand-yuan final payment, after taxes and platform commission, would leave him with around nine thousand in hand. Added to his remaining savings, it would cover two months of Xiaoman's medication. But that was only just enough. If Old Zhao choked the acceptance review, if Chen Hao's project fell through, the chain would still snap. He could not gamble on luck. He could only lock down the variables one by one.

By evening, the numbness in his foot had spread into his calf. He stood and took two steps. His knees softened and he nearly collided with the IV stand. Catching himself on the wall, he slowly sat back down. Xiaoman was awake, watching him in silence, only tugging his blanket a little higher. Lin Chen poured a cup of warm water and fed him two small sips.

“Does it hurt, ge?” Xiaoman's voice was very soft.

“No.” Lin Chen shook his head. “Just busy with something.”

“Your hand is shaking.”

Lin Chen lowered his gaze. His right index finger was indeed trembling faintly. Too long in the same position—muscle fatigue. He slipped his hand into his pocket, clenched it, then let go. “Go to sleep. It'll be better tomorrow.”

At eleven that night, the ward quieted down. He kept processing the second batch of data. The log scrolled on; the error rate fell to 4.1 percent. He set an automated verification script to compare field distributions before and after cleaning. The differences were within a reasonable range. He leaned back in his chair and closed his eyes. Outside the window, the city lights were sparse, like coordinates scattered in the dark. He knew Old Zhao would weigh his options. Either acknowledge the numbers, or replace him. But replacing him meant breaking in someone new, and the time cost would be even higher. What Lin Chen was betting on was the other man's anxiety about efficiency.

At one in the morning, his phone lit up. A WeChat message from Old Zhao: “I looked at the batch-processing logs. Efficient work. But the client says they won't accept records where the timestamp is NULL. This batch will be settled at 70%. Three thousand will be deducted from the final payment. Can you accept that?”

Lin Chen stared at the screen. Three thousand. Exactly the out-of-pocket gap for one month's levetiracetam. His fingers hovered over the keyboard, but he did not reply immediately. He opened his notebook of mistakes, turned to a blank page, and wrote: “Rule 213: Clients will always test the bottom line. Countermeasure: don't argue right or wrong, present evidence only. Delivery standards are based on the contract/email. If the other party breaches the agreement, preserve logs and pursue arbitration or terminate cooperation. Bottom line: do not compromise on the core pricing rules.”

Then he replied: “The original data dictionary did not mark timestamps as mandatory fields. Cleaning logic was executed as agreed. If completion is required, that constitutes secondary development and requires a supplemental agreement. This batch should be settled at 87.3% based on valid record count. Please process the remaining balance difference through corporate payment procedures. Attached are the verification report and log screenshots. Please confirm.”

Sent. He turned off the screen and leaned against the wall. The corridor lights had dimmed. Outside the window, a night bird swept past with a brief, sharp cry.

His phone vibrated again. A WeChat message from Chen Hao: “Weekend meeting moved to Saturday at 10 a.m. Location: the café in China World Trade Center Tower 3. Bring two things: first, an explanation of the data-cleaning architecture you've already run successfully; second, your understanding of compliant desensitization for government and enterprise data. The client is a municipally owned SOE, and their audits are strict. Don't bring a laptop—just bring your brain.”

Lin Chen looked at those two messages. One was survival. The other was ascent. He got to his feet, and the moment his left foot touched the ground, a sharp stab of pain flashed through it before sinking back into numbness. He walked to the window and opened a narrow crack. Night wind poured in, carrying the city's distinctive dusty smell. In the distance, a few office towers were still lit, like coordinates suspended in the dark sky.

He returned to the bedside, opened his laptop, and created a new folder: Government-Enterprise_Midplatform_Compliance_Desensitization_Plan_v1. Then he began drafting the outline. Desensitization was not as simple as masking; it was the layering of field-level access control, dynamic watermarking, and differential privacy. He needed to turn all the pitfalls he had stumbled through over the past three years into a reusable rule library.

The wind had already risen. The next step—whether to walk against it or borrow it and fly—would depend on whether the ground beneath his feet was solid enough to bear his weight.