5.13.2008

a day in the life


a day in the life.


11am. the sun is pouring through my windows. most of SF has been up and at it for hours. i'm on seven hours of sleep...with the aches of the previous nights service just starting to creep into my bones. i hesitate about rolling out of bed, but I soon realize my pre-work clock is ticking. I get up, wash the press pot, and grind my coffee.

12pm. i've had my coffee, read SFgate, and fed the rabbit. the coming work day is racing through my head: what to prep, what's been working, what hasn't been. i flip through cookbooks, watch tv, then get ready for work.

1:05pm. there are no medium coats on the rack. an average Nopa day lasts 13 hours...so a proper fitting shirt becomes pretty important. i opt for the dishwasher shirt/bib apron. downstairs, Alejandro is already reviewing the menu and checking the prep list we wrote the night before. we sit down and finalize the menu, then get to work on the prep list we've written for ourselves.

3pm. between the menu, bar menu, and "taste", it's been a busy few hours. add into that a general lack of room and equipment, and you've got a hectic situation. the a.m. shift starts to phase out, and the p.m. cooks start coming in. sometimes delegating to the cooks is the hardest part--the idea that something is being missed always hangs in the air. lists are written, crossed off, and re-written. conversation and hello's are brief at best.

4pm. the menu has been written, proof read, and printed. no turning back now. if we haven't prepped correctly, or are low on ingredient, we will truly look like assholes.

5:30pm. line up. 90% of the menu is cooked and tasted. the bar menu has been going for half an hour. if a cook isn't in the window with their mise at this point, you know it's going to be a long night. typically, the dishes work--or are easily fixed with a bit of salt, acid, or herbs. pressure builds during this half hour before service, and after chugging a 5:55pm iced coffee my heart and mind are both racing. no matter what, I always get a slight panic-y feeling just before service. i've had it since I started cooking...always reassured by the knowledge that once service started, I would lose the nerves and feel...normal.

7pm. service starts easily enough. despite the bar and community table being packed pre service, i've been mostly firing first courses. Guests are slow to sit, and a crowd builds at the door. By 6:45 my top rail is filled with main courses that have yet to fire. The noise level rises, and my printer starts to chatter.

7:45pm. the first and second pickups were easy enough, but now i'm looking at a 40 guest/45 dish pickup. a call goes something like "fire eight fish, six pork sets, six pastas, five lamb, three chicken, and greens. I re-read the tickets a dozen times, check in with each station, then pick up the order. this is a hectic time in the kitchen. as soon as it looks like things are slowing down, you get slammed again. mistakes made now are glaring, and can quickly send a service spiraling downward.

8pm. paul turns to me and says "hey rich, only five more hours." in most restaurants, five hours constitutes a whole service. by this time, we've already served almost 180 people.

10:30pm. the tickets die down...slightly. a cook has just enough time
to re-stock their station, get a drink of water, or go to the bathroom.
not both though. the never ending sound of the printer taunts me from
the app station: tickets are builiding up on first course again.

11:30pm. we've sold 40 fish and fifty burgers. the restaurant is roaring.

12am.
in between pick ups, cooks ravenously eat their dinners: pastas,
burgers, flatbreads. industry folks start to show up, and the mood in
the room changes. a beer is starting to sound really good.

12:45am. a five top shows up.

1am.
seating has stopped. we still have three tickets hanging, not to
mention possible desserts. cooks clean, sweep, and put away mise. i run
upstairs to start the prep list. you can actually hear the music over
the noise.

1:30am. alejandro and I have finished the next days
menu and prep list. cooks finish up their cleaning, and only a handful
of guests are left. i give danny five bucks to grab me an asahi. we just did well over 400 covers.

2am.
it's done. the kitchen is clean, orders are called in, and the walk in
is locked. my feet are throbbing. i walk out to the bus stop, where all
the cooks meet after service. danny hands me my asahi, and we talk shit
about the previous night, and try to unwind. some foh show up, and
everyone shares a slug of jameson. being "family" is such a restaurant cliche, but at Nopa, it feels true.

2:15am. i drive al home, and we re-cap the nights service. in my experience, nothing is as valuable as a sous chefs view on a nights service...so us bouncing our own experiences off each other can only lead to better services. i see alejandro more then i see my wife...so us being on the same page is extremely important.

2:30am. im home. i kiss my wife and sit on the couch. this is only the third time i've sat down in thirteen hours. my apartment is quiet...and it's eerie. without the constant din of the restaurant, it's hard to relax.

3:40am. i take my shower and go to bed. joey will call me the next morning, but i'll miss his call. between sleep and work, i'm only left with 4 hours a day to myself...so it's hard to see friends. this must be why nopa feels so....close. we really have no other choice.

10:40am. it starts all over again.

5.01.2008

A Hard Service.


A Hard Service.


Every cook has experienced it. The never ending tickets, fish burning, sauces breaking, running out of mise with the chef screaming in your face. A flood of emotion washes over you: frustration, anger, and embarrassment. Then the second seating comes in.

In the beginning, they're all bad services. Coming into your new kitchen job, you can barely recognize a quart container, much less run your own station. The longer time goes on, the better you become. Eventually you get promoted to sautee, and the bad services start all over again.

Soon you get a hang of things, and the bad services start to go away. Personally, I got to a point where the tiniest thing would ruin a service for me...feeling like I had cheated at some point--but most cooks just settle in and start to focus on technique and attention to detail.

But the bad services come back. It might be a rookie server making mistakes, a rush of diners sitting all at once, equipment breaking down, all while you work with a hungover dishwasher and that cranky extern on pantry.

What most cooks can't see is how important it is to experience nights like this. Too many good services can make a cook complacent...lazy even. A bad service stays with you the rest of the night. You dwell on it...and focus in on every little thing that went wrong. When you come back the next day, you're sharper than the knife in hand...and you know you won't let your previous mistakes happen again. Even if what went down was out of your control, you've thought of a plan to work through it--to adjust your routine. You start to learn how to feel out a night.

A hard service will teach a cook some of their most valuable lessons. The ability to re-assess and adjust is what seperates a good chef from a great one. A group of cooks that has had these experiences together, and learned the same lessons together will have the potential to be great as well.





notes.


  • Its May. Peas and favas are just showing up. WTF
  • Fish in Sausalito. Expensive + Cash Only + $5 toll back into SF = let's not go there anymore.
  • 42 inch lcd screens are awesome.