He Solved Everything Except How to Feel

3:17 a.m. The whiteboard in the conference room was covered with numbers.

Four rounds of discussion, and the sales figures were still dropping. Operations blamed the channels. Product blamed pricing. Marketing blamed the competitors. Everyone was right. Everyone was explaining the same thing in their own language.

He hadn't spoken. He drew three lines on his notepad.

The first was the policy cycle. That line ticked up every eighteen months, and right now it sat at the bottom. The second was channel inventory. Downstream distributors weren't holding stock, not because they couldn't sell, but because the batch they'd been forced to take last year was still sitting in their warehouses. The third was the competitors' pricing anchor. They were about to close their quarterly books and had already started discounting.

He finished, turned the notepad around.

The noise in the room stopped for two seconds.

No one asked him, "How did you figure that out?" Those three lines sat there, and all the earlier arguments automatically reclassified themselves as "details" rather than "causes." After the meeting, walking down the hallway, he heard someone behind him say, "Oh, that's what it is." He said nothing.

He never explained to people how he saw these things. The cost of explaining was too high. To explain those three lines, he would have had to walk through every quarter's data fluctuation over the past six years, the decision‑making inertia at every link up and down the supply chain, and the behavioral patterns that everyone in the industry took for granted but never put on paper. By the time he finished that explanation, the next meeting would have already started.

So he usually just gave the conclusion.

Once, someone talked to him for seventeen minutes about a project proposal. That person used a lot of adjectives, a lot of "I feel like." He listened, then restated the other person's entire need in three sentences. The first said the goal. The second said the obstacle. The third said the thing the person hadn't yet clarified for himself: "what I actually want more of."

The person stared. "How did you know?"

He didn't answer. He lowered his head and pressed his fingers against his temples. That gesture meant: while you were speaking, I was running probability corrections in my head. Every word you said, I adjusted once. Every pause, I added a new variable. By the time you finished, I'd run the model three times.

But he didn't say that. It wouldn't have helped if he had.

He looked down from the balcony of an apartment, deciding whether to buy it.

Other people looked at the sunlight and the price. He stood there for five minutes and saw: the foot traffic density at the coffee shop downstairs between 7:40 and 8:10 a.m. That window determined whether he'd need to leave fifteen minutes early to avoid the crowd. He checked the data for the morning subway congestion coefficient – at this station you had to let three trains pass before you could squeeze on. The property contract didn't mention the rooftop water tank's replacement frequency, but he asked the security guard, who said, "Hmm, I think it's been about two years since the last cleaning." He also noticed the positions of the two neighboring units' outdoor air‑conditioning units – their exhaust vents faced his balcony, and he wondered whether, late at night, they might generate a resonant frequency at a specific pitch.

He ran through all that, then bought it. Six months later, not one of his judgments had been wrong.

He didn't think this was anything special. He was just not very good at "not thinking."

Once, at work, there was a project with a skewed resource allocation – whoever took the lead would most likely take the fall. He knew that clearly. But he voluntarily handed it to the colleague in the next cubicle.

The colleague was grateful. The colleague thought he was a good person.

He didn't explain. He needed this colleague to stay at the company. Not out of affection – because the adjacent business line was planning an expansion at year‑end, and he needed someone to absorb some of the fire in the middle. This colleague had a stubborn personality and never backed down – exactly the best shield for the job.

On the day he handed over the project, he ran into the colleague in the break room before leaving. The colleague clapped him on the shoulder and said, "Thanks, brother." He smiled. That smile meant: you don't have to thank me. We're each just running our own numbers.

But he also knew: he ran his faster than the other guy.

The company's travel reimbursement policy was very detailed.

He never violated it. But within the bounds of compliance, he always claimed an extra 27 yuan. Not out of greed – he was testing a threshold. He tested it for three years and found that 27 yuan was the "see‑no‑evil" threshold for the finance department's manual review. One more yuan, and the system would flag it. One less, and that gap didn't exist.

In those three years, he was never once called in over that 27 yuan.

Until one time, he needed to buy three extra days to handle an emergency. He followed the normal process, every step compliant, except that on the timeline fields he used that gap he'd spent three years mapping. Three days. Enough. He didn't explain why he needed those three days. What others saw was a routine approval. What he saw was a covert channel he'd spent three years digging.

What he handled in those three days saved the entire department's quarterly performance.

No one knew the connection between the 27 yuan and those three days. He didn't plan to tell them.

The day his mother was hospitalized, he did three things after the call.

First, he looked up the hospital's pricing structure and the tiered reimbursement ratios of the medical insurance. Second, he asked the nurses' station for the shift schedule and noted the times when the aides changed over. Third, he walked the shortest route from the ward to the pharmacy and calculated exactly what time to queue at the window to save twelve minutes.

Then he sat down beside the hospital bed. His mother was asleep. The monitor beeped.

He sat there for four hours. He treated the hospital as a system, and he understood it well. Well enough to know when to renew the fees, when to change the medication, when to raise the head of the bed exactly fifteen degrees.

Then he stood up to go get a pot of hot water.

At the door, he paused.

He realized that in those four hours, he had never once been "worried." He had handled everything, but he hadn't worried. He had merely computed. Efficiently. Precisely. Dispassionately. The way he handled all of this was the same process he used for the three lines on the conference‑room whiteboard, for the 27 yuan on the reimbursement form, for the project he'd given away.

He stood at the door. The kettle was in his hand.

He thought: Is a person who doesn't worry still a son?

He thought about it. No answer.

Then he thought: A person who is wondering whether he's a son is probably not much of a son.

He walked out and filled the kettle. The water boiled. He poured a cup. His mother was still asleep.

The next morning, he sat by the bed and peeled an apple. He peeled it very slowly. The skin didn't break. He didn't know why he was peeling it so slowly. Simply because peeling an apple was one thing his brain couldn't compress into a model.

He finished peeling. He cut the apple into small pieces. He placed them on the nightstand.

Then he sat back. He thought of nothing. He just sat there.

That was probably the only moment that day when he didn't feel like "him."