And yes, the “pressure” jokes will be a regular thing, just get used to it! Now that that’s out of the way, shall we just proceed to the recipes? I thought so…


I am always inordinately pleased when my final product looks exactly like the picture in the book; it’s one of the reasons I disdain cookbooks that don’t feature full-on Playboy-quality food porn photos. The images should make your mouth water, am I right? Such was the case with Jeffrey’s Blue Ribbon Chili. Maybe I didn’t fill my bowl to the brim with the liquid for a photo op (since no one can actually eat it served that way!) but I guarantee my version looked spot-on, and I couldn’t wait to taste it. Particularly since I was convinced I had ruined the whole thing right out of the gate. Read on…
I decided to prepare this chili to serve on poker night hosted at our place, in part because at the time our good friends were staying with us and I had access to another excellent cook! There are 23 ingredients in this recipe, and I needed the extra hands to make it quicker to throw together (thank you Lisa!) The author claimed prep could be done in 15 minutes, but I call BS on that statement. That being said, there was nothing “difficult” about it, just a lot of chopping, spice measuring, and can opening. Speaking of chopping, that’s where I messed up royally, and thought the entire pot might be destined for the trash can. Or a warning label. The chili veggies included onion, garlic, poblano, jalapeño, and the coup de grace, a Scotch Bonnet or habanero pepper. The first time I used habanero my hands throbbed for four days, and I had only made a few slices. I learned my lesson, so this time I wore gloves as I carefully seeded and deveined the pepper, then diced it into bits, dumping the entire pile in to sauté along with the other peppers. Imagine my horror when I got to the very last line in the first instruction, “If you used it, remove the habanero and discard”. Oh. Crap… What unholy wrath of white-hot habanero oils had I unleashed into the unsuspecting pot?? There was no retrieving the minuscule pieces I had thoroughly incorporated into the mix, and I was devastated. During all the enthusiastic prep work, I failed to carefully read the very important line, “1 habanero, sliced in half, seeds removed”. I figured I would be eating cereal for dinner, given my particularly spice-averse palate. Hanging my head in shame, I carried on and completed the recipe, so I could share my humiliation with you, dear readers. You’re welcome. Once the pressure cooking was done, my sous-chef volunteered as sacrificial lamb…er…taste-tester…to see if it was acceptable, since she does like spicy food. Imagine my surprise when she proclaimed it both delicious and not spicy at all! Say what?!? Of course I had to try a bite regardless, based on my self-imposed rule of “always taste the recipe no matter what I think”. I figured at least she hadn’t spontaneously combusted, so that was a good sign. Relief (not tears!) flooded me when I tried a spoonful and did not immediately breathe fire. It was flavorful! It was comforting! It was EDIBLE!! That was really all I could ask for, but I got much, much more. So let this be a reassurance to you that you can’t really screw up Instant Pot recipes! 9/10 (for sneaking that habanero direction in there without writing it in 30-point font!)

Soooo… Turns out you CAN screw up Instant Pot recipes! My mistake. Or at least, “my poor choices”. My sister made her IP Mac and Cheese the last time I visited, and it was fantastic. I’ve made my own IP version in the past, probably from some online recipe search, and it was fantastic. This… wasn’t. In fact most of it did end up in the trash, much to my chagrin. It looked good, it smelled good, and yes, it was identical to the centerfold… I mean, cookbook photo! But all was not right with the world. I think the problem was that I was given too many options, and I chose poorly for the tastes of my household. We are all big fans of blue box mac and cheese in my family, so you’d think sodium wasn’t much of a problem, despite what my blood pressure readings would have you believe. I actually don’t care for salty food, but those commercially processed products are so sneaky! I’ve never felt that Kraft makes an overly salty dish, even though it packs 710mg of sodium per cup of prepared yumminess, and I eat half the box at minimum! This recipe however, was unpleasantly salty. Let’s start at the beginning to see where it went off the rails…
Step one was “choose your noodle”, between macaroni (obvi), cavatappi, or cellentani. Well, I’d never heard of that third one, and I had a box of cavatappi at the ready, so I picked that. I shouldn’t have. Not for the salt issue, but because it didn’t seem to cook all the way through during the prescribed time of 6 minutes. It should be noted that I prefer my pasta cooked slightly over al dente, and this came out definitely under al dente. Not crunchy, but close enough to be annoying. Next error in judgment: “4 cups chicken broth or garlic broth (e.g. Garlic Better Than Bouillon)”. I have low-sodium chicken broth and I should have used it, but I fell under the spell of gaaaahhhhhlic. I love it, and usually that is a safe bet. However, I only recently found the directions for the ratio of water to bouillon base – on the lid, not the label; WHY?? – and I was a bit heavy handed. Strike two. Garlic can definitely read as salty or spicy (if raw), and I should have known better. Next was 4 cups of cheddar, followed by 1/4 cup Parmesan. Again, cheese is salty, but nevertheless I decided to “use up the whole thing” from the Parm container. Strike 3. By the grace of God I did not have any Boursin cheese in the fridge, or I would have dumped that in too and had a real disaster on my hands. I did toss in the (“optional”; see, there he goes, giving me enough rope to hang myself!) cream cheese (105 mg sodium), and the “optional” hot sauce (150 mg sodium) and dijon mustard (115 mg sodium). Typically homemade mac and cheese calls for mustard powder instead of prepared mustard. I think I found the reason! While this looked creamy, cheesy and amazing, I could only eat a small amount due to the saltiness, and the hubby ate a relatively small portion for him, then reported he didn’t feel that great later, so he refused to touch another bite. The daughter unit is typically teenager-picky and wanted the neon orange stuff she’s used to, so she wasn’t fan. Long story short, no one really liked it. This is a cautionary tale; I don’t believe the recipe is necessarily at fault, but I will try this again only with major edits and substitutions. I give my attempt a 4/10, but it has potential! Choose…wisely.

Sadly, I must concede that every recipe is not unicorns and rainbows. I mean, who wants to eat a unicorn anyway? But seriously, I was a little disappointed with Dijon Dill Pork Tenderloin, and I didn’t even dork it up! It started innocently enough; I had thawed pork tenderloins, and the index conveniently showed several entries for my main ingredient. Great! I can’t say mustard sauce is the first flavor profile I associate with pork, but I wasn’t against the idea. Traditionally I roast pork tenderloins whole in a stoneware pan, and it is always juicy and perfect. To my dismay, cooking it in the IP made it a bit tough. Maybe it was the 10-minute natural release time that pushed it past its peak tenderness? Maybe I should have seared the meat before poaching it in chicken broth? Whatever the issue, I didn’t think it was my best work. The dijon “sauce” was actually more akin to a “soup”. It made so much sauce… We poured it on the pork, we drowned the mashed potatoes in it, and I still dumped a lake of it in the trash after we all ate a portion plus had the leftovers. 6/10, for not quite nailing all a pork tenderloin can be.
Despite the less-than-stellar reviews of two-thirds of this week’s recipes, rest assured that you should still get an Instant Pot! I have continued to make and enjoy the vast majority of recipes from The Step-By-Step Instant Pot Cookbook, and I have every confidence I will find even more absolute winners. I’ll just be more wary whenever I see that dangerous word, “optional”!





































