Monday, November 30, 2020

Around the World Cooking Journey

As we explore our world through the Around the World Cooking Challenge (AtWCC), follow along on our adventures here!

Note: We acknowledge that a complete list of nations is not without controversy. As of the time of conception of this challenge, we are planning to cover 197 countries, 50 states, DC, and the 5 permanently inhabited territories of the USA. To figure out what counted as a "country" for these purposes, we looked to Sporcle and how they made the determination of what would be included in their countries of the world quiz. (We have no affiliation with Sporcle other than enjoying their quizzes.) We used that not because Sporcle is the ultimate authority on the matter, but mostly because (a) their explanation made sense, and (b) it's the list of countries that M committed to memory long ago. For more on their methodology, go here.

(Last updated 1/4/2024)

General Cooking Challenge Posts
Country #1: Afghanistan

USA #1: Alabama

USA #2: Alaska

Country #2: Albania

Country #3: Algeria

USA #3: American Samoa

Country #4: Andorra

Country #5: Angola

Country #8: Armenia

Country #35: Chile

Country #36: China
- Macau: minchi

Country #46: Denmark

Country #50: Ecuador

Country #63: Georgia

Country #64: Germany

USA #14: Hawaii

Country #74: Hungary

Country #76: India

Country #82: Italy

Country #84: Japan

Country #87: Kenya 

Country #94: Lebanon 

USA #21: Louisiana

Country #110: Mexico
(Oaxaca)

Country #116: Morocco

Country #138: Philippines
- Tortang giniling (beef omelette)

Country #139: Poland
- Golabki (cabbage rolls)

Country #149: Samoa

Country #169: Sweden

Country #175: Thailand

Country #180: Tunisia

Country #181: Turkey

Country #187: United Kingdom

Country #195: Yemen

Sunday, November 29, 2020

Week 46 - Seasonal

I love fall seasonal dishes, whether it's a warm, hearty stew or something often found on the table at Thanksgiving, like mashed potatoes, green bean casserole, or stuffing. I wasn't sure what to make for this challenge, but like some of the other challenges, somehow it found me instead. We had ordered delivery from Whole Foods, requesting a Napa cabbage to make some moo shu, and they messed up and sent us a green cabbage instead. Although we could have used it in the same dish, we had coleslaw mix left over from something else that worked better, so we were then left with a green cabbage. Not wanting it to go to waste even though we received it in error, what should we do with it? Cabbage rolls!



Cabbage rolls were one of those things we always thought about doing, but knew it would be a lot of work. We found a recipe on Pressure Cooking Today that seemed to make it a little simpler because it used the Instant Pot, but we knew this had to be a weekend project because it would take at least a couple of hours. (It took more than 3 hours.) Originally, I was thinking it could be a seasonal dish because it was warm and soupy and filled with comforting flavors, but after reading the Wikipedia entry, it seems like a common dish that many cultures serve near Christmas. Definitely appropriate for the seasonal challenge! Also, although cabbage rolls turn up in many cultures, these seem to line up most closely with the Polish version described there (meat and rice stuffed in a cabbage leaf with a tomato-based sauce), which is what we were thinking when we made it as well.

We only made a few variations to the original recipe, but no ingredients photo this time because we were just trying to get a lot of moving pieces going and didn't really have space on the counter with the Instant Pot already out. Also, even though I was sort of considering this for the seasonal challenge before we made it, I didn't actually decide on it until partway through. Anyway, the ingredients we used were:

For the cabbage leaves and filling:

- 1 box of Trader Joe's chickpea and red lentil risoni ($2.99)
- 1 large head of green cabbage (technically $0 because it was given to us in error, $1.77 if we had purchased it)
- 1 yellow onion, finely chopped ($0.79)
- 1/2 head of garlic, minced ($0.33)
- salt and freshly ground black pepper ($0.03)
- 1 package of Impossible Burger ($7.99)
- 1 flax egg ($0.08)


For the sauce:

- 2 tbsp butter ($0.18)
- 1 yellow onion, chopped ($0.79)
- 1/2 head of garlic, minced ($0.33)
- 2 cans (14.5 oz) of diced tomatoes with juice ($1.78)
- 8 oz can of tomato sauce ($0.50)
- 1/4 cup white vinegar ($0.10)
- large spoonful of chicken bouillon ($0.25)
- garlic powder ($0.03)
- freshly ground black pepper ($0.02)
- a tsp or so of Worcestershire sauce ($0.08)
- cornstarch and cold water ($0.10)

The total cost of the meal was about $18.14, which covered dinner for the three of us (although B didn't eat a ton of it) plus a bowl of leftovers for another day. Not the cheapest meal, but using Impossible Burger pretty much guarantees that since it's $8 by itself. Using ground turkey or some other ground meat would probably knock that total under $15, a more standard amount for our dinners, but we like splurging with Impossible Burger every once in a while.

To make the cabbage rolls, the first step was to get all of the components in motion. We made the risoni on the stove, cored the cabbage and then boiled it for 10 minutes, and then started on the sauce (melting the butter, adding the onion, then the garlic, then everything else other than the cornstarch-water mixture). This sounded simple, but as we expected it to, the cabbage preparation part took a while. Once it boiled (and cooled a little), we had to pull off the outer leaves. After boiling the rest some more, cooling and pulling off more leaves, some of the remaining leaves from the inside were chopped up and added to the sauce when it was done. That was the instruction from the recipe, although if I were to do this again, I would add all the remaining cabbage into the sauce. It came out so tender from the Instant Pot that I would definitely just throw it all in there if there were cabbage remaining. The last piece of preparing the cabbage leaves was something A picked up from YouTube, which was to pare down the stem a little bit to make them easier to fold and roll.


Once the cabbage leaves were ready, it was time to make the filling by combining about 60% of the risoni, the Impossible Burger, onion, garlic, salt, pepper, and the flax egg in a large bowl. When the filling was ready, it was time to roll! I don't know why I thought this would be the most time-consuming part. Once we got the technique down (add a couple tbsp of filling to the bottom stem part of the leaf, roll up once, roll both sides in, then keep rolling away from you, putting it seam-side down on a plate/cutting board when done), it went pretty fast. I also found it really meditative to do.


We didn't end up using all the filling in our 14 rolls, so the rest of it I just threw on the stove and made "burgers" to snack on while the Instant Pot worked. Since the filling was designed to be eaten inside cabbage with the sauce, it wasn't the most flavorful, and I probably liked it more than everyone else in the household. Maybe I just like the taste of Impossible Burger plain. Snack was that, plus some of the leftover risoni, plus some of the leftover cabbage which I just stir-fried for a little while.


Back to the cabbage rolls. It was time to fill the Instant Pot, and here, we followed the instructions carefully to make sure everything would cook correctly. We put the rack on the bottom of the pot, then added a cup of water, and put the first layer of rolls on the rack. It only fit six, but I did pick the six biggest ones. Next up was to cover them with about 1/3 of the sauce. The second layer of rolls was then added, alternating the direction from the first layer. The rest of the sauce was added on top and around the sides of the rolls, being careful not to go past the fill line. (We were close, but not past it.)


We set the Instant Pot to high pressure for 18 minutes, and then followed the instruction to unplug it and let it naturally release (although we did 10 minutes instead of 15) before doing the quick release. It took quite some time to come up to pressure, and the quick release sprayed more water out than usual, so maybe we should have waited the full 15 (but it was late and we wanted to get going).


Once the rolls were moved to a separate plate and the rack removed, the Instant Pot went back on, but this time on the saute function. The cornstarch-water mixture was added (twice, so no idea how much I used) to thicken the sauce while it boiled for about 10 minutes. We topped the cabbage rolls with the sauce, and dinner was finally served (near 11 pm)!


So, how did the cabbage roll experiment go? Really well, especially considering it was our first time making them. I think the only things we would do differently next time (besides starting earlier, as we're still getting used to estimating total time when using the Instant Pot) would be to: (1) season the filling a little bit more, maybe adding some garlic powder or other seasonings, and (2) add all of the remaining cabbage (chopped up) into the sauce. The tomatoes and cabbage in the sauce were so tender, and the flavor of the sauce was like tomato soup. So comforting for the season. The cabbage leaves were also super tender, and the whole dish really worked and would be so good with those two slight modifications. I don't know when we would make this again because of how labor-intensive and time-consuming it was (so I'm counting it for Poland for the AtWCC now), and also because B doesn't currently seem to be a fan of cabbage or Impossible Burger (has only really eaten it 1/4 of the time we've served it), but we (A&M) were really satisfied with the final product. 

Wednesday, November 25, 2020

Around the World Cooking Challenge Update

Writing this post about changes to our plans for the Around the World Cooking Challenge gave me a bit of deja vu. Our original plan had been to go alphabetically through the world (including the states of the United States), cooking each place as a unit and learning as we went. It was going to be a long process, but I liked the structure of going one unit at a time. After all, if we tried something in-between for another country and liked it, why wouldn't I want to make it again years down the line?

This sounded a lot like our original plan for WorldEats, except that was going geographically on a walk around the world instead of alphabetically. We were only going to count visits for each country when we were "doing" that country. Theoretically, it sounded like a good idea. In the first few units, for Canada, Cuba, and Jamaica, it forced us to visit places on our list that were further from home, places we had always wanted to go but were too lazy to plan visits to in advance, and the experience was really rewarding. (We were much more spontaneous diners then, not really schedulers or reservation people for the most part.) But there were so many good places along the way, many that are no longer with us, that deserved a place in the WorldEats exploration, so we revised it, gave up on the geographic walk, and decided to just count anything that felt "worthy" to us

Cuba WorldEats! One day, we will get around to posting about this cubano with yucca fries. We went to that restaurant two or three times, so it would be "fresh" when we wrote the post, but we never did...

Well, the same thing is happening again. I made some dishes that were really good and would absolutely, 100%, be part of the AtWCC if I had been up to that country's cuisine, so why not count it? I'm not throwing all the structure out the window, as I'm still generally following the alphabetical framework, but if things pop up in-between that should count for other countries, then they will.

What types of things would "count"? Not an exact science, but some ideas. First, if it's an iconic dish from a country's culture, or something really popular or widely eaten, or just something that would have come up in my research as a must-cook, then it should qualify. Second, if it turned out well enough that I would be satisfied with it if we were doing that unit, then it should qualify. Third, and the thing that kind of pushed me in this direction, if the dish were really labor-intensive, took a lot of time to make, and was more of a special project, then it should probably qualify. Last note, unlike WorldEats, I'm not going back in time to pull up every recipe I've ever made that would count, but just anything from the date we decided to do the AtWCC and forward.

These will count for Lebanon!


I made some Karelian pies for the Finnish challenge in the 52 week cooking challenge. Put nicely, they did not turn out well. I want to try making them again sometime when I would hopefully do a better job. I am not counting those.

I made shish tawook for the Lebanese challenge in the 52 week cooking challenge. (Yes, a lot of this challenge modification was prompted by themes from the 52 week cooking challenge.) The skewers were amazing, and while I would make these again without hesitation when we got up to Lebanon, we are still in A (and the beginning of the letter A), so it might be a while. I am counting that.

I made chicken zorbian for the Yemeni challenge in the 52 week cooking challenge. (I am many posts behind...) It turned out pretty well, Y is very far away in the alphabet, and it was a lot of work. I don't know if I would make it again when we got to Yemen, but part of that is because I could just order it for less than $20 on DoorDash from our local Yemeni restaurant. Theirs tastes better, and it supports someplace local. I am counting that.

This is from one of the A locations. What do you think it is?

So, where are we on the Around the World Cooking Challenge anyway? I am clearly very behind in posting about our culinary adventures, so it should come as no surprise that that applies here too. We started in A with Afghanistan and then moved on to Alabama. I think we're most of the way through Alabama with a couple remaining things we want to try, and then it'll be on to Alaska. As far as posting, we haven't done any of those, and the only posts on this challenge are just us talking about it and not cooking anything. Need to get on that. The next post about the challenge itself will be a running list of what we've done for the challenge (which should also be pinned in the sidebar), and you'll notice that the first entry there isn't for a place that starts with A at all. Hopefully we'll catch up on some of these cooking challenge posts before the year is out!

Sunday, November 22, 2020

Strawberry Oat Frozen Dessert

Between my lactose intolerance and B's allergy to eggs, we don't buy very much regular ice cream anymore. Lucky for us, Trader Joe's keeps coming out with new vegan ice creams to try, made with different types of plant-based milks. One of the ones we tried earlier this fall was this strawberry oat frozen dessert with almond brittle and candied strawberries ($3.99). 


The base of the ice cream was oat milk, and the ingredients also included tapioca syrup, coconut oil, and agave syrup, with color provided by beets, annatto, and strawberries. This was the second vegan ice cream we tried from Trader Joe's, and we didn't like it as much as the other one (the vanilla one made with almond beverage that we still need to write a review for). A thought it felt more crystal-like and icy in texture because of the oat milk, while my biggest issue with it was the almond brittle. I found that I was still chewing the hard little bits of almond brittle even after all the strawberry flavor of the ice cream was gone, and I just wasn't a big fan of the almond brittle on its own. We liked the flavor of the strawberry ice cream itself, but noticed few candied strawberries. The overall ice cream was fine because the strawberry was good, but it wasn't as good as some of the other flavors, especially the vanilla.


Buy again? No. This was fine, but we prefer the vanilla-almond ice cream. If they were out of that one, we'd probably wait for it to come back or see what other new flavors TJ's comes up with next!

Thursday, November 12, 2020

Week 45 - Sous Vide

When the Week 45 challenge came up as sous vide, I was really happy that I wasn't officially participating in the challenge, because I had zero desire to do this. I participated in the sous vide challenge back in 2016, making some salmon that actually turned out really well, but there were a bunch of reasons I didn't want to do it this time:

1. We still don't have a sous vide machine, and the effort and attention required to rig up an alternative arrangement (beer cooler or oven or stovetop) and keep the temperature steady was more than my brain wanted to deal with at the moment.

2. The last time I did this with salmon, if it didn't come out right, I was okay with taking the small chance of something going wrong with A and I eating maybe raw, maybe sort-of-cooked salmon, but I'm not willing to chance that on our toddler's developing digestive system.

3. If I tried doing something sous vide and it did turn out poorly, it would have been a lot more difficult to put together a late plan B dinner with a toddler who needed to eat and had been surrounded by the sounds and smells of cooking for so long.

Honestly, I just didn't want to do it, and so I didn't. On to Week 46! (Or, on this blog, backwards to all the posts I haven't finished/written yet!)

Tuesday, November 10, 2020

Week 44 - Apples

The Week 44 theme, apples, came at just the right time in the fall season, but I wasn't sure what to make. I didn't really want to make dessert, but I'm also not a huge sweet-savory dinner person, plus uncooked apples aren't great for little kids (choking hazard), so what to do? I've been doing a lot of cooking events on Yelp, so the answer came to me instead. I signed up for a cooking class where they made a creamy chicken and mushroom dish using hard cider, so adapting that became our apples challenge!


I'm not going to put up a fully-written recipe, since it's not mine to share and I don't know a source to link to for the original recipe, but I'll briefly mention the ingredients and what was made. The ingredients I used (which were heavily adapted from the original, since not only did I not have hard cider, but I didn't have any apple cider, so I used apple juice) were:

- 2 boneless skinless chicken breasts ($7.18)
- salt and pepper for the chicken ($0.03)
- olive oil for the pan ($0.10)
- butter ($0.27)
- cremini mushrooms ($5.58)
- 1 red onion ($0.60)
- 2 large spoonfuls of minced garlic ($0.15)
- 8 oz package of apple juice ($0.30)
- chopped parsley for garnish ($0.40)
- heavy cream: substituted milk and butter ($0.54)
- 1 box chickpea rotini ($2.12)

Note that the cost for the milk/butter heavy cream substitute is much higher than it should have been, but that's because we had to do it the equivalent of 3 times. More on that later. The approximate cost of dinner was $17.27, which feels a little high for this dish, especially with apple juice instead of hard cider, but the cremini mushrooms and chicken from Amazon Fresh cost more than they would have if we had been able to get them from Costco or Trader Joe's.


To make the dish, you basically cook the chicken, browning it in the pan on both sides, then remove it, cook the mushrooms in butter, remove them to the same plate as the chicken, then add the onion and garlic to the pan with more butter, cook them down, add apple juice (hard cider, really, but apple juice for us) to reduce to start the sauce, then add the heavy cream, make the cream sauce, add the chicken and mushrooms back in, season with some freshly ground black pepper if needed, spoon over some cooked pasta, and then top with parsley to garnish.

Sounds straightforward, but we didn't buy heavy cream (not a fan of cooking with it in an attempt to keep a healthier kitchen), so I was going to substitute milk and butter. I tried mixing milk with melted butter like a recipe I found said to do, but it came out hard and clumpy with a consistency more like a grated radish. Into the trash it went. Then I remembered that I had previously added milk straight into some dishes without issue, so I did that, but then it curdled and we were left with clumpy bits of milk separated out from the liquid. Apparently that's edible, but it looked really unappetizing. I got a bit frustrated, thinking I had ruined our entire dinner, so A took over, heating up some milk in a separate pan on the stove and then adding it in to the sauce, fixing our sauce enough that you would never even know a mishap occurred. Grateful he was able to step in to fix my mini-disaster.


After the entire milk debacle and all of our substitutions, how was it? It was fine, but it won't make our favorite home cooking list anytime soon. I'm sure it wasn't nearly as good as it would have been using hard cider or shallots, some of the original ingredients, or actual heavy cream for a cream sauce. You could definitely taste that sweet apple juice that we added, which didn't really get balanced out by anything else, but at least the apples challenge dish tasted like apples!

Sunday, November 8, 2020

Week 43 - Food Mashups

The Week 43 theme was food mashups. I think when I first saw it, it was late at night, and I couldn't even comprehend what that meant. After reading some of the comments on Reddit, it made so much more sense. Cheeseburger pie, cheeseburger pizza, sushi burritos, baked potato pizza, the possibilities were pretty much endless. Honestly, it's also very similar to how we eat these days anyway, pairing all sorts of dishes with tots or pasta since they're easier for B to eat than some of the other smaller grains. I wanted to do something a little more composed though, so after reading over a few different recipes for taco pasta, I came up with a plan.


The ingredients for our food mashup were:

- 1 box of chickpea rotini ($2.12)
- 1 tbsp olive oil ($0.10)
- 1 yellow onion ($0.45)
- 1 red bell pepper ($1.50)
- 1 green bell pepper ($0.90)
- 1 heaping spoonful of minced garlic ($0.10)
- 1 package of TJ's beefless beef ($2.99)
- 3 scallions ($0.40)
- about 1/2 bottle of Pace mild salsa ($1.34)
- a few large spoonfuls of sour cream ($0.59)
- a few handfuls of shredded cheddar cheese ($1.20)
- taco seasoning: chili powder, coriander, paprika, salt, freshly ground black pepper, garlic powder, cumin, oregano (didn't measure, just eyeballed it and adjusted to taste) ($0.50)

It's a little hard to estimate the cost of this one since most of it was not measured, but the approximate amount was $12.19. It was enough for dinner for the three of us, plus a little extra for brunch the next day.


The steps for making the pasta were:

1. Prep - cook pasta, chop onion, chop red pepper, chop green pepper, chop scallions, make taco seasoning.

2. Heat olive oil over medium heat. Add onions and cook until translucent, then add peppers. Once peppers have softened a bit, add garlic, cook for a minute or so, and then add beefless beef. Add the taco seasoning, and make sure everything is mixed together well. Add water, a tbsp or so at a time, as needed if everything starts to stick at any point during the cooking process.

3. Add half the salsa and mix into the beef mixture. Taste and add seasonings if needed (didn't add anything here).


4. Add pasta into the skillet with the beef mixture, and mix together well. Add sour cream and the other half of the salsa, and make sure everything is coated well. Sprinkle in some cheddar cheese and stir in well. [I originally had only added a small amount of salsa, but after tasting it with the sour cream, it needed more. I like how it turned out, adding more salsa in this step, so I've written it as we made it.]

5. Serve in bowls, topped with additional cheese if desired!


You might notice that I haven't actually referred to the name of the dish in this post, only mentioning that I looked at recipes for taco pasta or that I made pasta. The main reason for that is that the name evolved as I was making it. I intended first for it to be taco pasta, more Mexican-style with onions and cilantro, but then I didn't want to buy a package of cilantro just for this (and also wasn't in the mood to clean and chop it). So I switched it to an American-style taco with chopped tomato and cheddar cheese, but then our tomato was just on the edge of going bad, so that was out. I thought maybe it should be burrito pasta, but there were no beans in it, so then I realized what corresponded best to what I made - quesadilla pasta! There was a beefless beef filling and cheese, plus salsa and sour cream, which you would normally find on the side of a quesadilla. Perfect name for our mashup.

As for the taste, we really liked it. I didn't think using the Pace salsa instead of just seasonings would make that much of a difference, but it did. Very happy with our choice to buy that, and that it added so much flavor while being mild enough for B to eat. Would make this again!