Quote

The hardest thing about being a full time chef is leaving my work behind when I go home at night. I'll toss and turn about a menu item or forget to order produce and wake up at 4 A.M. in a cold sweat over some artichokes.

Chefs don't eat at normal hours, so the only time you feel like you really need a meal is after service, when you're exhausted and just crave something to help you wind down.

I like to work at night.

I like cooking, but I don't think I could be a chef. Everyone from the ground up does terrible hours, whether you've just walked in off the street and you've got no experience, to whether you're the head chef. You can work 14 or 15-hour days. It's really, really intense.

I don't typically work that late into the night in a studio, I'm more productive during the day.

When you're a chef, you graze. You never get a chance to sit down and eat. They don't actually sit down and eat before you cook. So when I finish work, the first thing I'll do, and especially when I'm in New York, I'll go for a run. And I'll run 10 or 15k on my - and I run to gain my appetite.

I don't like to sit still for long at all, which has probably helped me along the way, and partly why I was drawn to the heat of a restaurant kitchen. The rush of service means that you're always on your toes and keeps a chef pretty active.

What's fun about chefs is that they're big guys, often, and they might not look like the most athletic people, but they're very powerful people, and they have tremendous stamina... It takes a toll on their body, too.

There are lots of things that keep me awake at night, but work isn't one of them. I mean, no-one's going to die if someone doesn't like what I do. So I don't feel a great pressure.

Writing is work and cooking is relaxing.