Is it a bug or a feature that my brain screams for sugar the second a production deployment goes south at 2 AM? I mean, seriously. I understand the biology of stress eating—cortisol spikes, glucose demands—but knowing the why hasn't stopped me from inhaling a donut while staring at a terminal window. So when I saw Made to Crave, I thought: okay, let's try debugging the source code instead of just patching the hardware.
I picked this up during a week of pure chaos at work (we're talking P0 outage territory). I needed something that wasn't another sci-fi epic or a dry business manual. I needed to know why my willpower crashes faster than a legacy server.
Debugging the Source Code
Here's the core thesis: We aren't broken because we crave things. The craving function is actually hardcoded into the kernel. The error is just a pointer mismatch—we're pointing that desire at food (or Netflix, or whatever) instead of spiritual satisfaction.
(Kevin, my boyfriend, would probably say my "spiritual satisfaction" is just optimizing Jira tickets, but let's ignore him for a second.)
TerKeurst isn't offering a diet plan here. Thank God. If I had to listen to another "eat kale, run more" lecture while stuck on the Caltrain, I might've thrown my phone. This is strictly backend work. She argues that until you fix the spiritual dependency, the physical output (weight loss, health) will always throw errors. It's basically a refactoring guide for your motivations.
And honestly? The logic holds up. Even if you aren't super religious, the psychological framework of "replacing" a craving rather than just suppressing it is solid engineering. You can't just delete a line of code and expect the system to run; you have to replace it with something valid.
The Voice in Your Headset
Let's talk about Jill Brennan.
She narrates this with a very specific "supportive friend at a coffee shop" vibe. Warm. Empathetic. Steady. For a lot of people, this is probably comforting. For me? I usually listen to hard-hitting tech bios or intense space operas, so this felt... soft.
I had to crank this up to 1.75x speed. At 1.0x, it felt a little too slow for my caffeinated brain. At higher speeds, her pacing actually works really well—she enunciates clearly enough that the speed boost doesn't turn it into mush.
One caveat though: if you're sensitive to that specific "gentle guidance" tone that borders on sweet, sample it first. I saw some reviews saying her voice grated on them. I didn't hate it, but it definitely felt like I was being spoken to by a therapist rather than a peer. Works for the genre, just know what you're signing up for.
Did the Patch Deploy Successfully?
So, did this fix my stress eating?
Look, I'm not gonna lie and say I'm cured. But yesterday, when the train was delayed (again) and I walked past the vending machine, I actually paused. I ran the diagnostic: "Is this physical hunger, or am I just trying to soothe a spiritual/emotional glitch?"
I didn't buy the Snickers.
That's a successful unit test in my book. The book can feel a bit repetitive—could've been shorter, maybe an email blast—but the message sticks. It's less about the food and more about why we use food to patch holes in our spirit.
Who Should Queue This Up (And Who Should Skip)
If you're looking for a tactical guide on macros, skip this. If you're looking for the root cause analysis of why you can't stick to a plan, give it a listen. I had a similar experience with Diary of a CEO—less about tactics, more about the underlying patterns that drive behavior. Just maybe speed it up a bit.
