Batch cooking

I already mentioned how I love batch cooking. It saves time, cooking fuel, and effort, allowing me to focus on other chores around the house on days I don't have to cook, but only reheat our previously cooked meal. 

People have mixed opinions about batch cooking. Probably the main misconception is that when you batch cook, you have to make do with a very repetitive way of eating. I don't necessarily think that we have to vary like in the way it's being propagated by most modern day nutritionists (fueled by the "food" industry). A so called "varied diet" is quite overrated in my opinion. The funny thing is though, people who think they eat very varied often are only doing so with their dinner while being very repetitive when it comes to breakfasts and lunches. Whereas for us, it's very rare that we eat the same breakfast for two days in a row. So I guess that despite batch cooking, we still do vary enough. 

If I batch cook a certain dish, we usually eat the same every other day. So, for example, if I make a stew on Monday, we have it again on Wednesday. And on Tuesday and Thursday, we either eat another batch cooked meal, or I make two separate meals. Two sperate cooked meals can happen because I don't batch cook every dish, although I do batch cook most of the dishes we eat. I also do is what I call "half batch cooking". I may cook up a pasta sauce and have it with different kinds of pasta and side dishes/protein sources. Or I steam a large batch of couscous and we have it with different sauces. Even if this method isn't strictly batch cooking, it still saves a lot of time, because more than half of the work has already been done. And an additional bonus is that it's still a bit less repetitive than eating the exact dish being eaten twice. 

I also batch cook ingredients such as the legumes that we use as a source of protein in many dishes. Since some legumes take up a long time to cook, it's best to cook them in larger amounts. As we speak, there's a pot of chickpeas boiling now. I'll devide that in several portions; a part for tonight's dinner and the rest goes in the freezer for later use. I do the same with lentils, despite the fact that they don't have nearly such a long cooking time. Even if it doesn't necessarily saves a lot of cooking time, it saves a lot of energy -and my sanity. If I make a legume based stew, I usually cook a double batch too. It doesn't go in the freezer usually, but we just finish it within a few days, not necessarily for dinner but for lunches too. I also keep small portions in the freezer for my mother in law, since she can't tolerate everything I cook, so I don't always have to cook separately for her. When baking bread, I also make bigger quantities and freeze is right after it's cooled down. That way, we can enjoy freshly baked bread with a bit less of effort. 

Some other concern which is mentioned often is food safety. Even though I have some anxieties when it comes to food, food safety of home cooked foods is not something I worry about a lot. If you think you get sick of eating certain foods, you will probably get sick (in most cases). The thing is, people are afraid of storing foods in the fridge and eat it within 3 days or so- to me, that's just silly. If that's the case, what do you need a fridge for anyway? Most vegetables will keep outside the fridge. In fact, some last even longer outside the fridge, when stored properly. I think most foods can be stored in fridges longer than the official guidelines says. I usually know how long a certain type of cooked food will last, based on experience. If I'm not sure whether or not I'm using up something that's been there for a few days already, and I'm neither planning to freeze it, I simply reheat it to the point that it's been boiled thoroughly. That way, foods can technically be stored for ages if it's then put away again in a new, clean container. Because any bacteria have been boiled dead, it's as if you've cooked up something freshly. By this method, I've rescued quite a lot foods from spoilage. I know this might be a bit controversial and certainly not officially advised, but it does work for us and I have no concerns whatsoever. 

The taste is yet another concern, and I find it a bit interesting that I've heard this concern more than once, because my experience is quite the contrary. In my experience, most dishes improve as they age. This is also why slow cooking methods are much better, taste wise. The faster food cooks, the less taste is has (with a few exceptions such as stir frying). Especially soups, sauces and stews taste much better the next day. This is why I sometimes make certain foods in advance. So in my opinion, this is another benefit of batch cooking; the next batch is even tastier! That's defenitely a win win if you ask me. 

When I was pregnant with my youngest (11 years ago... Time certainly flies!), I batch cooked a lot. The 2nd batch went directly into the freezer to have some quick meals during my postpartum period. It turned out to be very handy as I was hospitalized for a week after giving birth and my husband was taking care of our oldest daughter while being injured himself, after a car hit him. If you have a surgery planned, having a baby, or knowing you'll have an insanely busy time ahead for whatever reason, batch cooking and then freezing that food is really a good solution to still have homemade food with less effort. It's almost like a takeaway, but healthier and cheaper. And about everything can be kept in the freezer, you just need to know how to store certain foods. What I also love about batch cooking is that there's always foods for unexpected visitors. Yes, people will technically be "served leftovers" but I don't see a reason to be squeamish about that. It's not different than freshly cooked foods. And I've never heard that people had anything against it either, around these parts anyhow. 

So, despite all the objections people may have, I love batch cooking and will probably continue doing so for the rest of my life, as long as we have a fridge.