1. Expensive Option - Usually I just buy my lunch daily from the local supermarket / store.
2. Cheap Option - Buy stuff in a weekly shop and make lunch at home to bring in.
However recently I've been doing something I call "The Evolving Lunch".
1. Buy Ingredients / Lunch Items on a Monday, continue to add new Ingredients / Lunch Items as you run out of the previous items.
Monday - Buy a seeded bun, sandwhich filler and maybe a bit of salad.
Wednesday - Run out of buns and half way through sandwhich filler so buy wraps and cheese
Friday - Run out of wraps & sandwhich filler so buy some chicken pieces and make a salad.
So there we have it, what do you do for your Lunch office goers?
I've worked everywhere from corporate parks with nothing but a cafeteria within 30 miles, to wall street, midtown manhattan and now to Woodstock, where a good healthy carnivore would be hard pressed to find a reasonable piece of mostly-dead animal to eat.
No matter what the environment is, it always ends up, after about 3 weeks in the environment, distilling down to "one of 3 acceptable options":
1) Bad pizza
2) a "hey this isn't so bad" sammich
3) takeout asian food.
I've been trying to bring in food and eat like the Swanson to which I aspire. But it's pretty tough.
Maybe I just need to keep more ground beef and bacon in my filing cabinet.
I've done the 'evolving' lunch thing a bit. Ultimately I get tired of it because I still have to leave the office and drive off a few times during the week and it is less convenient than either bringing from home, or hitting a drive through.
I'm changing my habits currently to making lunch for the week. A change for me, as I have eaten out for the last decade (my make at home lunches don't really save much money, but are much better than the options around the office).
Well normally I bring my lunch to the office. However, the other day I went out to a local restaurant and sat at the bar as is my habit. Just so happened that the bartender that particular day was a rather attractive exchange student from that land down under. Gave serious consideration about not coming back to work. There is something about I love about that accent. Could have sat and listened to her talk all day long.
I'm pretty lazy and there's a filled baguette vendor who comes around our business park with a van, so I usually buy one from him. It's more expensive than making it myself but not massively and I earn enough that 5 lunches a week isn't going to do any damage.
If I have bread in the house then I'll make sandwiches with whatever I have (usually some kind of cheese and pickle variant), but I usually don't because I'm rarely in at lunchtime and that's the only time I really eat it.
Out once a week for a sit down; usually Mexican or Pho or similar. Subway a couple of times (it is about 50 yards up the road) or eat in as they provide food once or twice a week, usually. Now and again I might bring something in if I can remember to do it in a sleepy haze.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. Those who seek perfection will only find imperfection nils illegitimus carborundum
My wife makes me a delicious sandwich every day... Well, most days... Some days... Occasionally... Actually just the once this year so far so I go to BK across the road from my office or the market down the street where there is a variety of healthy salad stuff... which I ignore and get the Pretzel hot-dogs or the turkey-burger with fried onions, or the chinese buffet stuff or a deli-style sandwich with too much meat.
- I would love to change the world, but they won’t give me the source code.
In our office we dine together every day. We either send one of the staff out to pick up orders we phone in, or we cook something onsite. My office has a full kitchen, and we hire for cooking skill as much as business abilities. The last time we had a round of interviews, we selected a girl who makes a mean chicken fried steak over a girl who had her own business making personalized cupcakes. It was a good choice, as the one we hired has been expanding her culinary talents, and has mastered Mexican sauces and entrees, and various types of soup. I do Cajun dishes, smoked meats and prime rib, the GM does spaghetti and lasagna, the accountant makes excellent tacos, and all of us are handy with the grill.
While reading theDailyWTF the other day a contributor mentioned a pattern that he thought was a WTF and that was requiring object in constructors over id values.
Sorry, my example was too specific for people
ie public List GetLineItemsForOrder(Order order);
public static void DoSomeAction(Foo foo);
vs public List GetLineItemsByOrderId(Int64 orderId);
public static void DoSomeActionById(Int64 fooId);
Hopefully, my clarification will help focus people to addressing the specific question. But then, I have been here long enough to know; asking a question on this forum really never ends well.
To be honest I nearly universally prefer the former (requiring fully hydrated objects) In the 99% of cases where I write code, where absolute performance isn't critical, the first method is so much more reliable and easier for Junior developers to work with. (Less mistakes, more compiler errors, etc)
So, what say you? Remember, if you disagree you are wrong, also remember I do both depending on my mood so not only am I Intransigent but I am a hypocrite.