Site Status

Sticky post to inform new and returning readers of the following developments:

  • Site/server was compromised by some overambitious Bitcoin miners in mid-November 2017–we just got back online about mid-December 2017 (down for about a month). For more information, consult this entry.
  • Lost ALL images hosted by the site itself, but I still have them locally–working on rehosting/relinking images as we speak.
  • If you find yourself on a page with a (temporarily) missing recipe and you would like to see it, email me at simplydeliciouscookbook AT gmail DOT com and I’ll help you out.

I’ll update this page as progress is made. As of now (12/19/2017, 2 PM PST), the site is up, but there are still many recipes missing pictures. We have started posting new recipes however–check them out on the side bar or under this stickied post.

  • UPDATE – 12/23/2017, 6:15 PM PST – All entries from 2014 have been fixed. Starting on 2015…
  • UPDATE #2 – 1/1/2018, 11:15 AM PST – All entries from 2015 have been fixed. Starting on 2016…
  • UPDATE #3 – 1/11/2018, 9:45 AM PST – Still working on 2016, also fixing any entries that I see are getting hits, so there are scattered ones throughout 2016-17 that are also fixed. I haven’t given up–life (and a full-time job) just gets in the way sometimes.
  • UPDATE #4 – 1/20/2018, 3:45 PM PST – Jumped ahead to 2017 since that had less entries–all entries from 2017 have been fixed. Now to finish 2016…
  • UPDATE #5 – 1/29/2018, 2:45 PM PST – Still plugging away on 2016–I’ve fixed all of January through July, and a few scattered ones from August through December. Goal is to be done with it by the end of January, which gives me about 2 days to try to finish it up. Fingers crossed…
  • UPDATE #6 – 02/01/2018, 10:30 PM PST – Finally done! A day later than my goal, but that’s not bad. All entries from 2016 have been fixed, and with that, ALL entries have now officially been fixed. I’m unstickying this post, and filing it away as one hell of a learning experience.

Technical Difficulties…Please Stand By

Technical Difficulties…Please Stand By

Y’all, we got hacked.

A few weeks ago, I noticed the back-end stats of the website going wonky (insane amount of processes running, constant downtime notifications), and after some rudimentary detective work, I figured out that my site/space was being used for Bitcoin mining. My guess is they got in through a unsecured, out-of-date WordPress plug-in. Those SQL injections will get you every time.

I killed the site to stop the mining/resource hogging until I could figure out how to fix everything. Given the circumstances of the attack, we were able to save a lot of it (the posts, the overall structure, and the basic, un-tweaked version of the theme), but some aspects had to be dumped to ensure we got rid of every last bit of the bad code.

Unfortunately, one of the things we lost were any pictures hosted by the site itself. We had been working on moving pictures off to other storage spaces and re-linking them due to hitting my host’s space limits already, but I’d only made it up to about mid-2015 by the time we got hacked. My apologies for any recipes/pages you hit that have no pictures on them right now–I’ll be spending a lot of time over the next few weeks re-linking/uploading all the pictures for the posts. I have them all on my laptop, but I basically need to reconstruct about 2.5 years worth of work.

Thankfully, I didn’t have to say goodbye to over 3.5 years worth of work, time, and effort. I’m very lucky to have been able to save any of it, and even more lucky that it wasn’t worse.

Lessons learned:

  1. Don’t use a ton of WordPress plug-ins, and if you do–make sure they’re trustworthy, secure, and updated often.
  2. Watch your stats like a hawk–I could have caught this earlier, but I wasn’t paying close attention until the “SITE DOWN” emails started flooding in.
  3. Don’t just delete things willy-nilly when trying to stop the bleeding–I deleted an important database file when I was frantically trying to bring the site down and it cost me an extra week or so in downtime to repair that mistake.
  4.  BACK UP your site in multiple places–it’s an old IT saying: it doesn’t exist if there’s not at least two copies of it.
    • Backups helped in this case, but not entirely–the bad code was throughout the site, restoring blindly from a backup would have just started the problem over again. However, it’s still a VERY good idea, since we were able to pull the posts and some of the other essential parts out safely.

Thanks for sticking with me throughout my trials and tribulations. I’ll be getting back on track here shortly. Stay tuned!

Where the hell have you been?

Um, hi.

It’s been a while. A LONG WHILE. Anyone still left reading probably thought I gave up/got bored a long time ago. And truth be told, I did. I’ve spent the last year moving 400+ miles, leaving an old career, starting a new one, working as a line cook in a busy full-service restaurant, meeting new people, and learning my way around a new city. With all of this upheaval, it was tough to keep this thing going, and I’ve let it fall by the wayside.

There’s been a lot of tears, a lot of laughs, and a lot of changes. But one thing has remained constant: I still love to cook. So much so, that I’ve made it my new career. However, I’m no Top Chef, and I’ve learned that there are parts of the life I like, and some I don’t. One of those things I’m not a huge fan of is the hours–it’s really tough to work different hours from everyone else in your life. It’s also difficult to want to cook when you’ve spent hours in the back of a restaurant kitchen keeping up with its intense demands.

Where I’m going with this long rambling uninteresting mess is that I’m about a month into a new culinary job that has much better hours/pay and doesn’t leave me wanting to run away from all things cooking when I get home. And I realize that even though I’ve spent 25+ years cooking in some capacity, I definitely still have a lot to learn and practice.  So I’m kicking the tires, dusting off this old project, and restarting it again. I WILL finish cooking my way through this book, even if it takes me the rest of my life. So there.

Sorry it took me so long to come back. If you’re still there, thank you. If you’re finding this days, weeks, months, years from now, thank you too.

Let’s get this thing going again. Stay tuned. 😉



Here’s where I explain what this whole site is about. Settle in–there’s a bit of a story involved.

When I was a small child in the late 80s-early 90s just learning to cook, my mother gifted me with a set of subscription-based cookbooks called Simply Delicious. The set I currently have consisted of three “volumes” (although I’ve been told there are more cards/volumes out there–I don’t doubt it), and I believe I have a good amount of the cards that were produced. She (my mom) claims she gave up near the end. Thanks, mom.


Many of the cards have her notations on them, as well as mine. I come from a long line of cooks and restaurateurs, and we take our cookbooks seriously when we find good ones. They’re my go-to books for basic techniques, dinner parties, and just about any instance where you need easy, clear, traditional recipes. 📜

Front Cover

I’ve had these books for almost 30 years now, and they’ve been carted across state lines several times, existed in every kitchen I’ve ever had, and have generally just gotten really beaten up. They were even temporarily inhabited by roaches once when I lived in a really terrible apartment in the San Fernando Valley after moving back home to LA post-college graduation. 😱

I successfully evicted the roaches long ago, but the books aren’t exactly in the best shape. However, I still love them and haven’t been able to part with them, despite the roach residue that still coats the edges and corners. 💩


Given their present condition, I feel it’s time to scan them and retire the physical books themselves. Taking into account the current navel-gazing inclinations of our culture, I have decided to blog-while-doing, writing and cooking my way through the books as I scan them. I’ve cooked many of these recipes in the past, but I’ve never done the whole thing. 🏆

I call this giant time-suck: The Cookbook Project. It’s not original in any way. But considering there’s very little that I can find about these books out on the internet, I figure, what the hell.


Dive in, and enter the fanciful world of 1980s recipes-by-mail. I promise, most of the recipes are actually pretty good. You might even say they’re…..simply delicious.


Umm…I also promise to try to keep the bad memes to a minimum. 🙄