Ran out of green beans halfway through dinner service.. Ran out of potatoes a little after that.. Didn't run out of meat, chicken, or fish, but by the time the kitchen regrouped from the elementary mistake, it was took late: Food was ice cold.. gravy was coagulated.. But there were some really hot vegetables!
I can't quite figure out how professionals were able to misjudge and make food for 150 when a wedding was 250?
It was a disaster of a night.. Dinner service should have been an hour, it ended up being nearly two hours. Embarrassed servers didn't even want to leave the kitchen.. at one point people were hiding in shame near the entrance doors, trying not to be seen by the guests.. The first 10 or so tables were fine. Enough food.. nice and hot.. tasted great.. But that was only the beginning..
People began to get angry. But you know what's funny? They didn't get angry at the lack of food being served. No sir ree bobby.. they got angry at the bar being closed until after dinner was served. Which is understandable.. the lengthening dinner hour problem surely are into their getting drunk time.. Which is inevitably going to cause a group of people that get soothed by cold beer to get angry ..
Oh it was awful.. so very awful.. So bad. So very very bad...
But by 11pm, when the crowd left the building--leaving behind a very large mess and quite an odor in both restrooms-- it was over. All gone.. only memories to further pave the path of life. But this is one night of memories that will turn into a dreaded 'server dream' at some point soon...
Maybe it will be like INCEPTION and all of the servers I work with will be back in the same situation again in a dream together..
So very bad..
How the Smartphone Killed the Three-Day Weekend - How the Smartphone Killed the Three-Day Weekend: Interesting story. Now put your phone down.
9 hours ago