Chapter 190: Versions and Measures

The elevator stopped on the seventeenth floor. The metal doors slid open, but the sound-activated lights in the hallway did not come on. Lin Chen fished out his key, unlocked the door, and switched on the light. The air in the rental room was stale, carrying the smell of last night's takeout and damp plaster. He did not change his shoes. He went straight to the desk. The computer woke, its cold glow harsh on the eyes. The original design draft had to be submitted before nine. Version consistency.

He opened the company's internal document repository and pulled up the Data Middle Platform Scheduler V1.2 Architecture Design Draft from three months earlier. A PDF, eighteen pages. He flipped to page nine, the section titled “Retry Mechanism and Fault-Tolerance Thresholds.” The diagram was labeled: max_retries=3, backoff=exponential. But in the actual codebase, three months ago, to get the stress tests through, he had changed the threshold to max_retries=5, backoff=fixed. The change was recorded in the Git commit log, the commit message only a single line: hotfix: adjust retry strategy to accommodate stress-test peak load. It had not gone through change review. The design draft had never been updated.

This was technical debt. Most of the time it could stay buried, but the external consultant would be looking. Consultants did not read code. They read documents. If the documents did not line up, it meant a hole in the process. And in a promotion defense, a hole in the process amounted to “lack of engineering discipline.”

Lin Chen pulled open the drawer and took out his hard-cover notebook. He crossed out yesterday's fund entries and started a new page. 02:15 - 06:30: Refactor design draft V1.3. Complete change log. Align with codebase.

He opened the diagramming software. New canvas. First he dragged in the structural framework from the original diagram, keeping the core data flow intact. Then, beside the retry module, he added a dashed box labeled “Hotfix Patch Area.” He did not use words like “error” or “violation.” The survival rule of technical documents was to package what had already happened as an “evolution path.” He wrote the change description: V1.2.1 hot update: based on Q3 stress-test data, exponential backoff was adjusted to a fixed interval to reduce the probability that long-tail latency would block the cleansing pipeline. This strategy was validated through online gray release, with stability improved by 12%.

He weighed every sentence. No exaggeration, no concealment. Just facts, data, and results. He exported the new diagram and replaced page nine of the original PDF. Then he flipped to the appendix and added a Scheduler Parameter Change Traceability Table. It listed the time of change, triggering scenario, code commit ID, online monitoring metric comparisons, and rollback conditions. By the time the table was done, it was already four twenty.

Pain began to throb in his left foot. Not a cramp—more a dull ache from muscle ischemia after being deprived of blood flow too long. He stood up and went to the window. Pushing one half open, he let in the early-autumn wind, carrying the diesel smell of the city's outskirts. Holding the sill, he slowly shifted his weight onto his right leg, set the toe of his left foot lightly against the floor, and gently rocked it. As circulation returned, the pain receded into numbness. He went back to his chair and downed half a cup of instant coffee gone cold. The bitterness slid down his throat and made his stomach clench.

At five sharp, he opened the company shared drive and created a folder: Defense_Preliminary_Review_Materials_Technical_Architecture_Original_Design_Draft_V1.3. He uploaded the PDF, the change traceability table, and screenshots of the Git log. In the body of the email he wrote: The scheduler's underlying design draft has been submitted as requested by the consultant. Version V1.3 has been synchronized with the actual runtime parameters now in production; change details can be found in the appendix. If further branch verification is needed, I can join a call at any time.

Send. Time: 06:42.

He leaned back in the chair and closed his eyes. There was no relaxation in it, only waiting. At seven, his phone vibrated. Not HR. Not the consultant. His mother.

Chen, Xiaoman threw up twice this morning. She hasn't stopped the medicine. I asked your cousin-uncle about the provincial capital hospital registration—he managed to squeeze us in for next Wednesday morning. I fronted the train fare first. You just focus on your work.

Lin Chen opened his eyes. The screen's light reflected the dark shadows beneath them. He typed: Mom, don't front it. I'll transfer it. I'll definitely be there on Wednesday. Tell Xiaoman not to be scared—the follow-up is just procedure. He transferred 500. Balance: 682.5. He wrote it down: -500 (medicine/travel). Remaining: 682.5.

The numbers were shrinking. But the path was clear. Pass the defense, move up a grade, withdraw the housing fund, bring cash flow back into the black. The gears of turning technical work into money meshed tightly. He could not stop.

At eight-thirty, he splashed water on his face and shaved off his stubble. He changed into a pressed shirt. On his left foot he put on an old, roomy pair of sneakers, tying the laces very loose. Before leaving, he slipped the hard-cover notebook into his backpack. The elevator went down. In the mirrored panel, the man inside stood very straight, though his gait had a slight limp. He did not care. In the workplace, no one looked at posture. They looked at delivery.

At 9:05, he sat down at his workstation. The computer screen lit up. One prompt after another rang out from the internal messaging system.

The first was from the HR system: The external technical consultant has reviewed the V1.3 design draft. Version consistency confirmed. Note: the change traceability table is logically clear and in compliance with engineering standards.

The second was from Director Li: Two o'clock this afternoon, rehearsal. Bring the PPT and the alignment records. The consultant will sit in. Don't screw this up.

Lin Chen replied: Received.

He opened the PPT and went through the process one last time. Page seven, degradation strategy. Page nine, cost assessment. Page eleven, evolution roadmap. In the notes section of every slide, he had written out response language. He was not memorizing a script, only fixing the logic anchors in his mind. A technical defense was not a speech. It was Q&A. The sharper the question, the more the answer had to return to the data.

At eleven, Zhou Wei came over carrying a cup of coffee and set a printed document on his desk. “Final aligned version from the product side. I've signed it. If the consultant asks about business expectations during the rehearsal this afternoon, just turn to this page.”

Lin Chen took it. The paper was light, but it carried weight. This was a moat. Technology covering the base, product providing backing. If both sides locked in together, the review committee would have no real weakness to attack.

“Thanks,” he said.

Zhou Wei glanced at him. “You look awful. Is your foot acting up again?”

“Same old problem. Doesn't affect anything.”

She did not ask more, only turned and left. In a big company, concern was a luxury; boundaries were the rule of survival. Lin Chen tucked the alignment record into the hard-cover notebook. Opening a fresh page, he wrote: 14:00 - rehearsal. Core goal: validate the Q&A chain, expose blind spots, do not chase perfection.

At lunch break, only the hum of the air-conditioning was left in the office. He lay face-down on the desk with his eyes shut. He did not sleep. In his head, simulated questions and answers kept running.

“If the cache is penetrated, how does the degradation strategy keep the main transaction path from cascading into failure?”

“Three levels of circuit breaking. Level one: rate limiting. Level two: degraded fallback. Level three: static page. The core is isolation, not recovery.”

“If the retry threshold is raised to 5, won't that amplify pressure on downstream services?”

“No. With fixed intervals plus the upper limit of the connection pool, actual concurrency is controlled at 80% of downstream capacity. Monitoring and alerts are there as a safeguard.”

He went through the questions one by one. Anchored the answers one by one. There was no room for luck, only contingency plans.

At one fifty in the afternoon, he stood up. The numbness in his left foot was still there, but the muscles had already adapted to that imbalance. He walked to the meeting room and pushed the door open. Director Li was already seated at the head of the table, with two empty seats beside him. Zhou Wei sat to one side with her laptop open. The projector was on, throwing the first page of the PPT onto the white wall.

“Sit,” Director Li said without looking up, fingers tapping on the table. “The consultant had something come up and will join remotely. Just present. If I interrupt you, that's the question.”

Lin Chen sat down. Plugged in the USB drive. Clicked play.

The screen lit up. His voice was steady, with no rise or fall. From architectural background to core pathways to degradation strategy, he moved through it all. He kept the pace to about 180 Chinese characters a minute. He did not rush to speak, and he did not explain unnecessary technical detail. He spoke only in logic that the business side could understand.

When he reached page seven, Director Li suddenly raised a hand. “Stop. Here. If cache hit rate drops below 60%, level-two degradation is triggered. If the downstream service itself is already unstable at that moment, won't your degradation become the last straw that breaks it?”

Lin Chen paused for a second. Not because he was stuck—because he was confirming.

“No.” He pulled up a screenshot of the monitoring dashboard. “Before degradation is triggered, the system checks downstream health first. If the downstream is unstable, the degradation strategy skips that node directly and switches to static fallback. We don't put out fires. We isolate them.”

Director Li stared at the screen for three seconds. “Continue.”

Lin Chen turned the page. His voice remained even. In the meeting room there was only the sound of typing and the whir of the projector fan. Under the table, his left foot was tingling with numbness, but he pressed his weight into the back of the chair and kept his breathing level.

The rehearsal ended. Director Li closed his laptop. “The logic works. For the formal defense this afternoon, keep this pace. Don't add extra drama.”

Lin Chen nodded. “Understood.”

He gathered his things and walked out of the meeting room. The lights in the corridor were already on. His phone vibrated. A text had come in from an unfamiliar number.

Lin Chen, this is the technical consultant. I've reviewed the change traceability table in the design draft. There's one detail I'd like to confirm: why was the hotfix three months ago not processed through the standard change workflow? Before tomorrow's defense, I need a written explanation. This is not about assigning blame. It's a process review.

Lin Chen stood at the end of the corridor. Outside the window, the sky was darkening. One neon sign after another was lighting up across the city. He lowered his head and looked at the words on the screen. Process review. Written explanation.

He replied: Received. I will submit it before 8:00 tomorrow morning.

He put away the phone and slowly walked back toward his desk. His gait still limped slightly, but his back was very straight. There was another battle tomorrow. But tonight, he had to sleep four hours first. His body was the only capital he had. He could not overdraw it.

He turned on the computer and created a new document. Title: Explanation and Review of the Scheduler Hotfix Process. The cursor blinked. He typed the first line: Balancing the stress-test deadline against online stability at the time, I chose to apply the fix first and complete the process afterward. This was an error in engineering judgment and has been entered into my personal mistake log. For all future hotfixes, change review will be strictly completed in advance.

No excuses. No deflection. Just owning it.

Save. Shut down. Turn off the light. The rental room sank back into darkness. Only the sound of traffic outside the window came faintly through the glass. Like the tide, pushing people onward.