Chapter 197: Field Alignment

The cursor blinked in the terminal. He typed in the JOIN statement, linking the new table user_behavior_v2 to the old dimension table through user_id. The upstream documentation called it a “real-time stream,” but underneath it was actually micro-batch processing, with the time window compressed from T+1 to fifteen minutes. That meant he could no longer rely on a full scan; he had to add partition filtering. He appended WHERE dt >= '${biz_date}', his fingers striking the keyboard in a steady rhythm, like oiling an old machine.

His left foot twitched again beneath the desk. It was not pain, but numbness. The numbness crept up from his ankle along his calf, like countless fine needles moving slowly under the skin. He shifted his left foot from the low stool to the floor and planted it firmly. The chill of the floor seeped through his sock, pressing down, a little, on that floating agitation. He adjusted the angle of the chair back and shifted all his weight onto his right leg and tailbone. The time in the lower-right corner of the screen flipped to 14:17. There were less than forty-eight hours left until Friday’s two o’clock presentation.

He saved the script as etl_mapping_v3.py. Then he opened the terminal and entered the run command. The progress bar began to crawl forward. Log lines streamed past one by one: [INFO] Reading source table... [INFO] Joining dimension... [INFO] Handling nulls... He stared at the screen, breathing lightly. Data cleaning was not magic. It was blunt labor. Every field type conversion, every fallback for null values, every risk of a Cartesian product in a join—each one had to be trapped in advance. He created a validation script to check row counts, deduplication rate, and key field distributions after the batch run finished. The mindset of a mistake log had long since sunk into muscle memory: never expect it to run successfully in one go, only make sure that every error can be traced to a specific line.

A rustling sound came from next door. His mother was up in the night. Her footsteps were light, stopping at the bathroom door, followed by the faint sound of water running from the tap. Lin Chen did not look back. He simply minimized the terminal window and switched back to his PPT draft. There was still one last gap in the financial model’s conversion funnel: after the new table structure went live, the way user dwell time was measured had changed. The old logic counted page refreshes; the new logic counted session heartbeats. If he applied the numbers directly, the conversion rate would be inflated by twelve percent. He had to recalibrate the loss coefficient before tomorrow morning.

The terminal gave a soft beep. The batch run was finished. He switched back to the logs. [WARNING] 3,412 records dropped due to session_id format mismatch. He frowned. The upstream docs had not mentioned any change in the session_id format. He opened the PDF and flipped to Appendix Three. Sure enough, there it was in tiny print on the very last line: “After the mobile SDK upgrade, the session_id prefix has changed from mob_ to app_; legacy data requires regex replacement.” Forty-seven pages of documentation, with the critical information buried in the footer. He closed his eyes and took a deep breath. There was no time to complain. He opened the editor and added a line of regex replacement to the mapping logic: re.sub(r'^mob_', 'app_', session_id). Then he ran it again.

This time the progress bar moved smoothly. The validation script started. Row counts aligned. Deduplication rate: 99.98%. Key field distributions matched the expected normal shape. He leaned back in his chair and rubbed the space between his brows. Blue light from the screen reflected on his face, and there was a dry sting in his eyes. He got up and went to the kitchen for water. Passing his parents’ room, he saw the door half-open. His father was already awake, sitting on the edge of the bed with that tin pillbox in his hand, counting them one by one. Mecobalamin, vitamin B1, gabapentin. The foil strips had been punched into little empty hollows, like a dried riverbed. Hearing movement, Lin Jianguo looked up at him but said nothing. He only closed the pillbox and put it back on the bedside table.

“Dad, take them on time. Don’t cut the dose on your own,” Lin Chen said quietly from the doorway.

“Got it,” Lin Jianguo answered, his gaze falling back to the box. “Medicine’s expensive in the city. Save where we can.”

“You can’t save on this.” Lin Chen’s tone stayed even. “If nerve damage drags on too long, later you won’t even be able to hold a hoe. Don’t worry about the money.”

Lin Jianguo’s Adam’s apple bobbed. In the end, he only nodded. He stood up and nudged the slippers on the floor back under the bed, moving slowly, with the stiffness left behind by years of labor. Lin Chen watched his stooped back and said nothing more. He turned and went back to the living room, setting the cup on the edge of the table. The water had already gone cold. He took a sip. The bitterness slid down his throat, pressing down the sourness churning in his stomach.

Four in the afternoon. He went back to writing the stress-testing script. Once the new table’s JOIN logic crossed five million rows, memory usage would rise exponentially. He had to change the full-load read into a streaming read with chunked processing. He pulled up the chunksize parameter in pandas and set each batch to one hundred thousand rows. The terminal started running again. The hum of the fan swelled in the cramped rental apartment. He watched the task manager: CPU usage held at 75%, memory climbed steadily without spilling over. He let out a breath. There were no shortcuts in technology. You just broke big stones into little pebbles and carried them one by one.

At five-thirty, his mother was boiling noodles in the kitchen. The clicks of the induction cooker were very soft. Lin Chen walked over and turned the heat down. “Wait until the water’s really boiling before you put them in. Don’t let them turn mushy.”

“Got it.” Wang Guiying stirred the noodles with chopsticks. Steam rose and blurred her face. “Don’t stay up too late tonight. Your foot’s already like that, and you’re still staring at the computer.”

“I’m almost done.” He took the strainer from her hand. “Go rest. I’ll serve it.”

Dinner was simple: plain noodle soup with two leaves of greens. There was little conversation at the table. Lin Jianguo ate slowly, chewing each bite with care. Wang Guiying occasionally looked up at him, worry in her eyes, but did not ask aloud. Lin Chen knew what they were thinking. City work was not like farming. You could not see it or touch it, but it wore a person down all the same. He lowered his head and ate. The noodles were soft, the broth bland. When he was done, he washed the bowls. Water ran over the porcelain, foam fine and dense. He dried his hands and returned to the living room.

Seven at night. The stress-test data had finished running. He exported the results and generated the charts. The latency loss coefficient had been corrected to 0.87, expansion costs were capped within threshold, and the hash logic in the security desensitization process was fully closed-loop. The PPT’s framework was finally complete. He checked it page by page, confirming the data sources, formula references, and chart formatting were all correct. His fingers slid over the trackpad, pages switching smoothly. Everything was back on the rails.

At 8:40, he prepared to do one final full validation. The terminal started. The progress bar moved forward slowly. Then suddenly a red warning flashed through the logs: [ERROR] Data drift detected in segment 'tier_3_users'. Conversion rate anomaly: +4.2%. He stopped moving. The conversion rate for tier-three users was abnormally high. He pulled up the raw data and compared it row by row. It was not a script issue. It was the upstream event-tracking logic: behavior classified as “stayed on page for more than three seconds without clicking” had been wrongly counted as “valid interaction.” That meant if it went live as-is, Finance would see inflated conversion data, Operations would adjust ad spend strategy accordingly, and the actual ROI would come in below expectations.

He stared at the red line in the logs, fingers hovering over the keyboard. Fixing it required changing only one line in the filter condition. But once he changed it, the core conclusion in the presentation would collapse. Finance would question the model’s validity. Operations would demand a delay. Director Li would not listen to explanations; he only cared about the result. Lin Chen picked up his teacup. The water had gone cold. He put it down and opened a new document.

Title: “Explanation of Event-Tracking Definition Differences_V1”

He listed the anomalous data, the attribution logic, and the revised impact calculations point by point. No emotion, only facts. The workplace did not recognize hard effort; it only recognized closed loops. Laying the problem out in the open was safer than hiding it and waiting for it to explode.

At 9:15, he clicked send.

Recipient: Data Engineering Team Lead, Old Chen. CC: himself.

The moment the email went out, he leaned back in his chair. Outside the window, the night had deepened, and the city’s neon lights cast blurred blotches of color across the glass. His phone vibrated. A new message from Old Chen:

“Received. The definition issue has already been synced with upstream. Before tomorrow morning’s presentation, update the PPT with the corrected data. I’ll handle Director Li.”

He replied: “Understood. The data has been updated.”

He set the phone down and rubbed his left foot. The numbness was still there, but he was used to it now. He opened the calendar and marked tomorrow’s presentation time in red. The gears were still turning, but the meshing teeth had been realigned. He typed the final line of comment. The glow of the screen lit his face, calm and undisturbed.

Eleven o’clock. The light in his parents’ room went out. Their breathing was steady. He switched off the main light and left only the desk lamp on. In the terminal, the background validation script was still running. He leaned back in the chair and closed his eyes. Tomorrow was Friday. After the presentation would come a new cycle. He did not know what the next variable would be, but he knew that as long as the script could run through and the data could be aligned, the road could keep moving forward.

Suddenly, his phone screen lit up. A text message—from the county hospital’s neurology department, an automatic reminder:

“Patient Lin Xing (Xiaoman) follow-up appointment confirmed: 2014-05-18 09:00. Please bring recent EEG report and medication records.”

He opened his eyes and looked at the line of text. May 18 was Sunday. He would need to take leave. Train tickets, accompanying care, examination fees. In his notes app, he added a new line:

“Return to county on Sunday. Reserve transportation and examination budget: 1200.”

He typed in the number and saved it. At last the progress bar in the terminal reached 100%.

[INFO] Validation complete. All metrics within tolerance.

He closed the laptop. Outside the window, the wind threaded between the buildings, giving out a low, mournful cry. He had to get up early tomorrow. He lay down and closed his eyes. His breathing steadied. The night was deep.