Why I Learn From Chefs, Not Just Coders

"When you think of a chef, people only seem to picture an already successful one. No matter what profession you're in, the process is hidden. But what actually decides the success is the process."

— Chef Sung Anh

I didn't expect to find my most profound lessons about coding from watching Korean cooking shows.

The tech world obsesses over finished products. We celebrate deployed apps, viral launches, successful startups. But the 3am debugging sessions? The six failed attempts before the seventh works? That process stays hidden. Just like Chef Sung Anh said — we only see the successful chef, never the burned sauces that built them.

The Hidden Process

Chef Sung Anh — On what success actually depends on

Chef Sung Anh — Michelin three-star holder, judge on Culinary Class Wars — doesn't cook within boundaries or single genres. At Mosu, he cooks "what I think is the best, no boundaries, no genre." The InventStor system I built took 116 commits to get right. This portfolio's 3D lanyard took six iterations just to get the texture mapping right. None of that is visible in the finished product. But it's everything that built it.

Craft as Communication

Chef Son Jong Won — On cooking as structured communication

Chef Son Jong Won — the only chef in Korea leading two one-Michelin-star restaurants simultaneously — defines cooking as communication, not just preparation. Fine dining is "an exchange between the kitchen and guests." That's what I try to do with code. Not just to computers, but to future developers. The way I name variables, structure functions, write error messages — it's all communication. Some bugs require days of simmering thought. Some features need patient, meticulous building.

Fearless Fusion

Chef Choi Hyun Seok — On simplicity as mastery

Chef Choi Hyun Seok named his restaurant "Choi Dot" (최.) because his dishes "need no further explanation." His signature vongole pasta: olive oil, garlic, butter, clam broth, salt. That's it. Five ingredients, executed perfectly. The restraint is the flex.

This taught me something about code: complexity is not craftsmanship. My best functions are the simplest ones. The 3D lanyard looks complex, but the code is minimal — physics does the work, I just set the stage. Don't over-engineer.

I'm learning from chefs because they understand something tech culture often forgets: the hidden process is where the real growth happens.