Dust and Stars - 1992 | Chapter 218 | Front-Loading Variables | English
Four in the morning. The alarm hadn’t gone off; Lin Chen woke up on his own. Sleep had been like a sponge squeezed over and over—t
Chapter 218: Front-Loading Variables
Four in the morning. The alarm hadn’t gone off; Lin Chen woke up on his own. Sleep had been like a sponge squeezed over and over—there wasn’t much moisture left in it, but it was enough to reboot his brain. He sat up, and the familiar dull ache came from his left ankle. It wasn’t an old injury flaring up, but fasciitis caused by days of prolonged sitting and constant rushing around. He rubbed it without making a sound. Xiaoman was still asleep, breathing steadily. The green glow of the monitor traced regular arcs across the wall, its beeping slicing time into even fragments.
He moved quietly to the window and opened his laptop. The screen’s cold light reflected on his face, unable to hide the dark circles beneath his eyes. First task: the server vendor. He dialed the distributor whose number he had found the night before. The other party picked up quickly, voice hoarse with just having woken up. Lin Chen went straight to the specs: dual Xeons, 256 GB of memory, two 4 TB NVMe drives, colocated in a local data center, with a dedicated 10M bandwidth line. The quote came in 15% over budget. Lin Chen didn’t haggle. He only asked, “If we sign for six months, with one deposit and three months paid at a time, can we do corporate billing terms? Also, can the rack units reuse any idle slots you already have so we can skip the installation fee?” The other side fell silent for a few seconds, then came the sound of typing. “Mr. Lin, billing terms are negotiable, but it depends on your company’s cash flow. As for idle rack space, we do have two slots, but the network cutover will have to wait until Wednesday.” Lin Chen wrote it down. “Wednesday is fine. I’ll send over our credentials and a draft contract this afternoon. Keep the price you just quoted and round off the change.” He hung up. The first piece of the puzzle had fallen into place.
Second task: the third-party inspection report. Seven business days truly wasn’t possible, but insisting on fifteen might intensify the conflict. He opened his email and pulled up the message he had sent Chen Hao the night before. There was still no reply. He changed his approach. Fast-track channels at testing agencies were usually for “MLPS Level 2,” but this time the client wanted a code audit of the core module of the desensitization engine. He searched up two local laboratories with CNAS accreditation. Expedited service would cost eight thousand yuan, with a turnaround of five days. Eight thousand yuan—the contract didn’t specify who would pay. He couldn’t front it himself. He created a new document and drafted a “Security Testing Coordination Statement.” The core logic was simple: Party B would provide the complete codebase, deployment environment, and test cases; Party A had to assign a contact person to coordinate integration and complete an internal pre-check of the environment within three business days. If delays in testing were caused by Party A’s environment not being ready or by changes in business logic, the timeline would be extended accordingly, with additional fees charged separately. He attached this as a draft supplementary agreement to Appendix Three and sent the package to Chen Hao. Postscript: "Seven business days can be achieved, but only if Party A cooperates with the preliminary environment pre-check. The expedited fee should be borne by Party A, or offset against the second-phase payment. Please have legal review it. The final draft is needed before Friday's review meeting."
Third task: medication costs. He opened his banking app and confirmed that the term deposit withdrawal had arrived. Balance displayed: 7,834.30. Subtract the server deposit (estimated at 12,000, with only 3,000 due upfront under billing terms), subtract the reserved expedited testing fee, and his actual usable funds came to less than five thousand. He opened the WeChat mini-program for the off-campus pharmacy and ordered sodium valproate and levetiracetam. He chose “hospital pickup.” Payment successful. The system prompt read: "Medication has been reserved. Please bring your prescription and payment receipt to the outpatient pharmacy counter on the first floor before 16:00 on November 18 to collect it." He saved a screenshot and set an alarm.
Seven in the morning. Footsteps began to sound in the hospital corridor. A nurse pushed a treatment cart past, the rubber wheels making a rhythmic squeaking sound against the terrazzo floor. Lin Chen went into the bathroom and splashed cold water on his face. The man in the mirror had sunken eye sockets and stubble coming in. He shaved and changed into a clean shirt. The collar was a little tight, so he loosened half a button. When he returned to the room, Xiaoman was already awake, staring blankly at the cracks in the ceiling.
“Ge, what date is it today?” Xiaoman’s voice was a little hoarse.
“The sixteenth.” Lin Chen poured a cup of warm water and handed it over. “Lie down a bit longer. I’ll go get the medicine this afternoon.”
Xiaoman took the cup but didn’t drink, only looked at Lin Chen. “You barely slept again last night. The computer screen was on the whole time.”
“There’s a lot to deal with. Once it’s all sorted out, it’ll be fine.” Lin Chen didn’t explain further. He opened his notebook of mistakes and flipped to a new page. The pen tip came down:
"Article 218: The essence of resource exchange is risk transfer. Vendors want cash-flow backing, clients want compliance liability exemptions, pharmacies want prepayment to lock inventory. Cash flow cannot be interrupted, but it also cannot be concentrated at a single node. Server: one deposit, three months paid at a time. Testing fees tied to the client’s level of cooperation. Medication costs locked in early. Every variable must be converted into an executable SOP. Next step: confirm the testing contract before 3 p.m., verify the server installation checklist, and prepare the technical demo environment for Friday’s meeting."
Nine-thirty in the morning. Chen Hao’s WeChat message finally arrived. "Legal reviewed your supplementary note. Seven business days is acceptable, but Party A won’t accept the expedited fee. Mr. Wu’s position is that you issue the report first, and the cost will be deducted from the first payment. Also, at Friday’s CTO review meeting, the technical demo can’t just run scripts—it has to use real desensitized sample data, with no fewer than five hundred thousand records. Your local server won’t be cut over until Wednesday. Will you make it in time?"
Lin Chen stared at the screen. Deducting it from the first payment was essentially price suppression in another form. Five hundred thousand sample records meant that data cleaning and concurrent stress testing of the desensitization engine would have to be completed within three days. The local server wouldn’t be in place until Wednesday. The timing was brutally tight.
He replied: "The expedited fee will not be deducted from the first payment. It should go through an independent reimbursement process or be offset in phase two. The sample data can be run, but Party A must provide the original pre-desensitization dataset by end of business tomorrow. Otherwise, after Wednesday’s cutover there will be no data to test. Friday’s demo will present actual progress; we will not commit to concurrency metrics that have not been validated."
Sent. He put away his phone, knowing they would bargain further. But he had already drawn the line. The technology could be demonstrated, but the data source and the flow of funds had to remain transparent.
Two in the afternoon. He left the hospital. The early winter sunlight fell on the asphalt, casting a cold white sheen. He walked to the subway station. When his left foot touched down, there was still a slight sense of stiffness. He adjusted his stride and shifted his center of gravity onto his right leg. There weren’t many people in the subway, and he found a corner seat, opened his laptop, and began configuring the demo environment. Docker containers, desensitization algorithm modules, log collection plugins. Line after line of code went in, the progress bar on the screen advancing slowly. He didn’t need to show off. He only needed stability. Stability was the greatest competitive edge of all.
Three forty. He arrived at the pharmacy outside the hospital. He queued, checked the prescription, paid, and collected the medicine. The plastic bag felt heavy in his hand. On the way back, he passed a convenience store and bought two rice balls and a bottle of mineral water. Sitting on a bench in the hospital garden, he unwrapped a rice ball and ate slowly. The seaweed was a little crumbly, the rice slightly cool. But he ate carefully. Only when there was food in his stomach could his brain keep working.
Seven in the evening. Back in the ward. Xiaoman had already eaten dinner and was drawing on a discarded medical record book with a pencil. He had drawn several crooked little stars, and beside them he had written a line of tiny words: "Ge went to pick the stars." Lin Chen glanced at it without saying anything. He put the medicine boxes into the drawer and labeled them: "Morning/Evening, one tablet each, after meals."
He opened his computer and checked the server configuration list. The distributor had sent over a draft contract. The clauses were basically consistent except for one line: “If Party B fails to make the second-phase payment on time, Party A has the right to reclaim the rack space and erase the data.” He added a comment: "Data erasure requires thirty days' prior written notice and a data migration window period must be reserved for Party B." Then he sent it back.
Nine o’clock. The email notification chimed. It wasn’t Chen Hao; it was a confirmation email from the distributor. The contract had been stamped and returned. Server cutover: Wednesday at 10 a.m.
Immediately afterward, Chen Hao’s message popped up: "Mr. Wu just finished an internal meeting. Friday’s review has been moved up to Thursday at 2 p.m. The CTO is traveling unexpectedly. Also, the original dataset has already been packaged and sent to your corporate email—five hundred thousand records, including some unclean dirty data. You handle it yourselves. As for the expedited fee, Mr. Wu says we can talk about it after the demo passes."
Lin Chen looked at the string of words. The schedule had been moved forward by a day. Dirty data had been dumped directly onto them. The expedited fee was left hanging. Every buffer period had been compressed.
He took a deep breath and did not reply immediately. He opened the five-hundred-thousand-record data package and extracted it. The progress bar reached 100%. He randomly sampled one hundred records and ran them through the V3.0 script. Error rate: 12%. Missing fields, encoding conflicts, duplicate records. The usual old problems.
He created a new Excel sheet with the column headers: Cleaning Rules, Exception Type, Processing Time, Responsible Party. Then he filled them in. Reality had no miracles, only addition and subtraction. But this time, what was being subtracted was time, and what was being added was fault tolerance.
He picked up his phone and replied to Chen Hao: "Received. We will go live on time at 2 p.m. Thursday. The dataset has been received and is undergoing pre-cleaning. The demo environment will present the actual data quality without concealing issues. The expedited fee will proceed according to the original plan, and the process can move forward after the demo."
Sent. He turned off the screen and walked to the window. The city lights were still densely packed, like an enormous net. He touched his pocket. The cigarette pack was still empty. He didn’t need cigarettes. What he needed was to get up at six tomorrow morning, run the final round of stress tests, and set the fault-tolerance threshold of the demo script as high as it would go.
Xiaoman turned over on the caregiver’s bed, and the monitor kept up its regular beeping. Lin Chen looked at the cracks in the ceiling, already breaking down tomorrow’s task list in his head. The schedule had been moved up, but the logic hadn’t changed. Data didn’t lie, and code didn’t speak falsehoods. As long as every step was planted on solid ground, whichever way the wind blew, the sail would turn that way.
He returned to the desk and opened his notebook of mistakes. The pen scratched softly across the page.
"Article 219: When variables move earlier, contingency plans must move earlier too. Dirty data is not an obstacle; it is a test case. Thursday’s review meeting is not about perfection, but stability. Cash flow, compliance, delivery—three fronts running in parallel. The bottom line does not change."
He closed the notebook. His phone screen lit up again. It wasn’t a work message, but an automatic push notification from the hospital system: "Patient Lin Xing (Inpatient No.: 20190814) is scheduled for a follow-up EEG tomorrow. Please report to Neurology Room 1 before 8:30 a.m."
Lin Chen stared at the line of text. The review meeting was on Thursday. The follow-up was on Friday. The schedules had collided.
He turned off the phone and propped up his left foot again. The light in the ward dimmed completely, leaving only the green glow of the monitor casting a faint reflection on the wall. Tomorrow he had to run stress tests, verify the server cutover, and prepare the demo environment. The schedule was packed, but every step was still planted on solid ground.
Nine fifteen at night. He set the alarm for five in the morning. Before closing his eyes, he took one last look at Xiaoman. His younger brother was sleeping deeply, breathing evenly.
There was still a long road ahead tomorrow. But tonight, all he needed was four solid hours of sleep.
More from WayDigital
Continue through other published articles from the same publisher.
Comments
0 public responses
All visitors can read comments. Sign in to join the discussion.
Log in to comment