I Optimized Everything Except the Part That Matters

I can tell you my system.

Wake at 5:40. Gym by 6:00—push/pull/legs rotation, progressive overload, tracked in a spreadsheet. Cold shower (2 minutes, 50 degrees—the studies on norepinephrine are compelling). Breakfast: 40g protein, pre-prepped. Commute: 22 minutes via Caltrain, optimized by catching the 7:48 express instead of the 7:52 local.

I'm at my desk by 8:15. I write code. I'm good at it. Promoted three times in six years. My manager calls me "high-impact." My performance reviews contain phrases like "force multiplier" and "technical excellence." I've shipped products used by millions of people.

I had dinner alone last night. And the night before. And most nights this year.

My parents came from Seoul in 1991. My father was an engineer. My mother was an engineer. They met in a graduate program and built a life around the belief that excellence is a form of safety. If you are excellent enough—high enough GPA, prestigious enough company, large enough salary—the world cannot hurt you.

I inherited this belief the way I inherited my blood type. Without choosing it. It's in the architecture.

So I optimized. School: valedictorian. College: Berkeley, CS. Career: FAANG, then a startup, then back to FAANG at a higher level. Each transition was a calculated move. I A/B tested job offers. I treated my career like a codebase: identify inefficiencies, refactor, deploy.

And it worked. By every metric my parents would recognize—income, title, company prestige—I am a success story. Their sacrifice produced a staff engineer who maxed out his 401k at twenty-six. Mission accomplished.

Except.

There's a concept in engineering called "local maximum." It means you've found the best solution within a narrow search space, but the global maximum—the actual best answer—exists somewhere you haven't looked. You're optimized within your constraints, but your constraints are wrong.

I hit local maximum at twenty-eight. Everything in my career was dialed in. Green across the board. But when I zoomed out—way out, past the spreadsheets and the sprints and the performance reviews—the dashboard was red.

Friends: I have colleagues. I have Slack channels. I have people I eat lunch with who would not notice if I was absent for a week. I do not have a person I could call at 2 AM.

Relationships: I've dated. App-based, obviously. I optimized my profile. I ran the numbers on response rates by photo type and opening message length. I got matches. I got dates. I did not get the thing that happens when someone sees the messy, un-optimized version of you and stays anyway. Because I never showed them that version. I showed them the deployed build. The production version. No bugs, no debug logs, no error states.

Hobbies: I work out. Working out is not a hobby. It's maintenance. A hobby is something you do badly and love anyway. I don't do anything badly. I don't know how to let myself be bad at something without treating it as a problem to be solved.

Last month I went home for my mother's birthday. My father, retired now, sat with me on the porch and asked if I was happy. Not "are you successful"—he knows the answer to that. "Are you happy?"

I gave him the production answer: "Yeah, things are good. Work is going well."

He looked at me with an expression I'd never seen from him before. Tired. Not physically. Something deeper.

"Kevin," he said. "I optimized my whole life too. Your mother and I—we built everything around performance. We thought if we gave you the tools to succeed, happiness would be a natural output."

He paused.

"I think we forgot to include it in the requirements."

I didn't know what to say. My father—the man who taught me that emotions were inefficiencies to be managed—was sitting on his porch at sixty-three telling me the architecture was flawed.

I'm not writing this for sympathy. Staff engineers at FAANG companies are not a vulnerable population. I know that. My problems are first-world, high-income, embarrassingly comfortable problems.

But loneliness doesn't check your compensation band. The human need for connection doesn't care about your Leetcode score. And the particular loneliness of men who were taught that achievement is connection—that if you just perform well enough, belonging will follow—that loneliness is specific and real and it lives in a $2,800/month studio apartment in SoMa where the WiFi is excellent and the silence is total.

“Loneliness doesn't check your compensation band. The human need for connection doesn't care about your Leetcode score.” Click to tweet →

I've started doing something that feels absurd: I'm being bad at things on purpose.

I joined a recreational basketball league. I am terrible. I was the last pick. I airballed a layup in my first game and a guy on my team laughed—not at me, with me—and said, "We've all been there, man." And for a second, I was part of something that had nothing to do with performance.

I called an old college friend I hadn't spoken to in four years. I said, "I think I've been a bad friend and I want to be less bad." He said, "Dude, I thought you'd dropped off the earth. Want to grab dinner?" No optimization required. Just a sentence and a yes.

I told my therapist (new—I just started, obviously I researched seven before selecting one, old habits die hard) that I don't know how to be close to people. She said, "Closeness isn't a skill you master. It's a risk you take repeatedly."

“Closeness isn't a skill you master. It's a risk you take repeatedly.” Click to tweet →

Risk. I take calculated risks all day in my codebase. But emotional risk—the kind where you show someone your debug logs and hope they don't file a bug report—that's the one I never learned to ship.

I'm learning. The optimization framework doesn't apply. There's no A/B test for vulnerability. You just do it, badly, and hope.

This is my first draft. It's not production-ready. I'm deploying it anyway.