The Cook and the Coder

Anthony Bourdain didn’t just write about food — he wrote about the life around it. In Kitchen Confidential, he pulled back the curtain on a world most diners never see: the chaos, the camaraderie, the scars you wear proudly. He made the kitchen feel dangerous and alive, a place where you could burn yourself in more ways than one… and still come back for more.

I was hooked.

So when I found myself between careers — leaving a job as a risk product manager and not yet starting as a project manager — I saw my chance. A clean break. A window to try something I’d only ever read about. Not a cooking class. Not a hobby. The real thing: a shift on the line.

I started in the kitchen of a busy bar, a crash course in heat, knives, and urgency. Later, I moved to a high‑end Mediterranean restaurant where the food was refined, the pace was faster, and the expectations were higher. I went in thinking it would be interesting. I came out knowing it was one of the most intense and honest work environments I’d ever been part of.

And the thing is… the lessons I learned there have never stopped applying — even in software.

Kitchen rule: Always work clean.
In software: Keep your codebase clean. Mess breeds chaos. Chaos slows you down. Technical debt is the unwashed chopping board that will poison tomorrow’s service.

Kitchen rule: Working with your hands means you leave work at work.
In software: When you focus deeply, you finish the task, commit it, and move on. Mindless context‑switching is like walking away from the grill mid‑service — something will burn.

Kitchen rule: A well‑oiled kitchen runs on collaboration and clear communication.
In software: Call out blockers. Pair on tricky problems. Share context early so no one is blindsided in production.

Kitchen rule: Respect the mise en place.
In software: Prepare your environment and tools before you start. Dependencies, test data, local build — all ready before you “fire” your first commit.

Kitchen rule: Sharp knives, sharp mind.
In software: Keep your tools — IDE, scripts, automation — sharp. Old, blunt tooling bleeds time and breaks your flow.

Kitchen rule: The heat is constant — so keep your cool.
In software: Production incidents are just another dinner rush. Stay calm, follow the process, and don’t make things worse in the scramble.

Kitchen rule: Taste everything.
In software: Test continuously. Don’t ship what you haven’t “tasted.” If it’s wrong in production, it’s already too late.

Kitchen rule: Don’t burn bridges.
In software: Tech is a small world. Your teammate today might be your hiring manager tomorrow.

The kitchen taught me discipline, focus, and the strange peace that comes from being utterly present. The same skills that get you through a dinner rush are the ones that get you through a product launch. Both worlds reward preparation, precision, and teamwork. Both will punish sloppiness instantly.

And in both, there’s that moment at the end — when the last ticket is out, the last bug is fixed — where you can exhale, wipe down your station, and walk away into the night, free until the next shift.