The 310 Calories I Was Drinking Before 9 AM and Never Counted

For months I was proud of how clean my food logging was. Every plate got photographed. Every snack got counted. And the scale still sat stubbornly around 212.

Here’s the part that stings: I never once logged my coffee. In my head, coffee wasn’t food. It was just… the thing I held while I got my day started.

Quick disclosure, since it matters here: I’m the founder of ZeroToHero (zerotoherofit.com), the app I use to log my meals, and I’ve gone from 232 pounds to 208 with it. So when I tell you I missed something in my own logs, I’m telling you about my own product’s blind spot too. The app can only count what I tell it about.

The week I counted the drinks

One Sunday I decided to run a boring experiment: for seven days, log every single thing I drank that wasn’t plain water. No judgment, just numbers.

Here’s what a normal morning looked like:

A 16-ounce mug of coffee, about 10 calories on its own
Three heaping spoonfuls of a flavored creamer, roughly 150 calories (the serving size on the bottle is one tablespoon, and I was nowhere near one tablespoon)
A second mug mid-morning with a splash of oat milk and a teaspoon of sugar, around 70 calories
A glass of orange juice with breakfast, 80 to 100 calories depending on how generous the pour was

Add it up and I was drinking about 310 calories before 9:30 AM, every day, with zero protein and zero fullness to show for it. Over a week that’s over 2,100 calories, which is more than half a pound of fat I was never accounting for. My daily target in ZeroToHero (zerotoherofit.com) is built around a deficit of roughly 500 calories, so a 310-calorie blind spot was quietly eating more than half of it.

Why liquid calories are so sneaky

The problem isn’t that creamer is evil. It’s that drinks don’t register the way food does. Nobody finishes a mug of coffee and feels like they ate breakfast. So your brain doesn’t dial back later, and you eat the same lunch you would have eaten anyway.

The second thing is that we pour by feel, not by measure. I measured my “usual” creamer pour into a tablespoon once, out of curiosity. It was three tablespoons. The label wasn’t lying. I was.

What I changed (and what I didn’t)

I did not quit coffee. I tried that once for four days and was a miserable person to live with. Here’s what I did instead:

Swapped to one measured tablespoon of half-and-half. About 20 calories instead of 150. I use an actual tablespoon from the drawer, not my eyeballs.
Dropped the sugar from the second mug. It took about a week to stop tasting like punishment.
Ate the orange instead of drinking the juice. Same fruit, about 60 calories, plus fiber, and it actually fills me up.
Logged the coffee anyway. A photo of the mug takes two seconds, and the habit keeps me honest.

The new morning total is about 90 calories, down from 310. That’s 220 calories a day back in the bank, or roughly 1,500 a week.

What happened to the scale

I didn’t change anything else that month. Same dinners, same weekend rules, same walks. Over the next four weeks my trend weight went from the stuck 212 range down to just under 209, a loss of a little over three pounds from a change that cost me almost no willpower. I’m not going to promise you’ll get the same number; your mornings are different from mine. But I’d bet money there’s a drink in your day you’ve never counted.

Try this for one week

Don’t change anything yet. Just log every non-water drink for seven days, with honest pours. Then look at the total. If it’s under 100 calories a day, great, you can skip this whole post. If it’s closer to what mine was, you just found the easiest fat loss of your life, because you can fix it without eating a single thing less.

That’s the whole reason I built ZeroToHero (zerotoherofit.com) around logging first and judging later. You can’t fix a number you’ve never looked at. Mine was hiding in a coffee mug.

The Number I Ignored for Months Was Fiber — and One Lentil Salad Changed My Lunches

I’m Jason, I’m down from 232 to 208 pounds, and I built ZeroToHero (zerotoherofit.com) because I was tired of guessing what I ate. So you’d think I’d have my numbers dialed in. For months I watched two of them: calories and protein. I never once looked at fiber.

Then one Sunday I scrolled back through my ZeroToHero (zerotoherofit.com) logs just to see what the nutrition breakdown looked like for the past two weeks. My fiber averaged about 14 grams a day. The usual guidance for adults is roughly 25 to 35 grams, and the dietary guidelines work out to about 14 grams per 1,000 calories, which for my intake meant I should have been closer to 28. I was at half.

What 14 grams a day felt like

Here’s the part I only connected afterward. My lunches were the weak spot. A turkey sandwich on white bread, a handful of chips, maybe an apple if I remembered. About 450 calories, plenty of protein, and about 3 grams of fiber. Two hours later I was in the pantry. I’d written that off as a willpower issue for a long time. Looking at the log, the lunch just wasn’t doing much to keep me full.

I’m not a dietitian and I’m not claiming fiber is a magic fix. I’m telling you what I saw in my own numbers: on the days my lunch had more fiber, I snacked less in the afternoon. Not zero snacks, but fewer.

The lentil salad that made it easy

I didn’t want to overhaul everything, so I picked one meal to fix. I landed on a Mediterranean lentil and roasted carrot salad, which takes about 35 minutes and makes two servings. Here’s what goes in it:

4 medium carrots, sliced into half-inch pieces, tossed with 1 tablespoon olive oil, 1/2 teaspoon cumin, and a pinch of salt
Roast at 425°F for 20 to 25 minutes, turning halfway
1 1/2 cups cooked lentils, drained
2 cups arugula
1/4 cup crumbled feta
1 tablespoon lemon juice and 1 more tablespoon olive oil
2 tablespoons pumpkin seeds on top

Cooked lentils carry roughly 15 grams of fiber per cup, so even a three-quarter-cup serving gets you around 12 grams before the carrots, arugula, and seeds add more. When I logged my bowl, the total came to about 15 grams of fiber for a single lunch. That’s more than I used to get in an entire day’s worth of lunches and snacks combined.

I use canned lentils, rinsed, on busy weeks. Dried work too, but canned means this is a lunch I’ll actually make on a Tuesday. It also keeps in the fridge for three or four days, and I think it tastes better on day two once the lemon has soaked in.

What I’d tell you before you try it

Go slowly. I jumped from 14 grams to 30-something in about three days and my stomach let me know about it. If you’re starting low, add fiber over a week or two and drink more water. That’s the one thing I’d do differently.

Also, don’t swing too far the other way and start treating fiber as the new thing to obsess over. What I took from this is smaller: I’d been measuring only the numbers I already had a habit of watching. Looking at the full breakdown showed me a gap I’d never have guessed at.

After about three weeks of eating the lentil salad three or four lunches a week, my daily fiber average was sitting near 27 grams. My afternoon pantry trips dropped from nearly every day to maybe twice a week. The scale kept moving at its usual slow pace, which is what I wanted. No drama, just a lunch that stopped working against me.

If you want to see your own fiber, protein, and calorie breakdown without doing the math by hand, that’s exactly what I made ZeroToHero (zerotoherofit.com) for. It isn’t in the app stores yet, but you can find it at the site. And since I’m the one who built it, take my enthusiasm with that in mind. The lentil salad, though, you can make tonight with no app at all.

ZeroToHero keto garlic butter salmon bowl recipe card

Why I Never Went Full Keto — Even Though Half My Dinners Look Like It

People see the plate — garlic butter salmon, a scoop of cauliflower rice, no bun in sight — and assume I’m keto. I get it, and I get why they’d assume it: I’m the guy who built ZeroToHero (zerotoherofit.com), so surely I’m running some optimized low-carb protocol behind the scenes. I’m not. I tried, actually, and the reason I quit is a better story than the diet itself.

Back in April I ran keto for real — 16 days, carbs capped under 20 grams, logged every gram in ZeroToHero (zerotoherofit.com) because I wanted actual numbers, not vibes. Bacon and eggs for breakfast, salmon or ground beef for dinner, cheese as a snack, a tablespoon of peanut butter felt like a luxury. I lost 3.4 pounds in those 16 days, which sounds great until you look at what came with it. By day 6 I was flat — not hungry, just foggy, like my brain was running on battery saver. My gym sessions fell apart: I dropped from 185 for five reps on bench to barely grinding out 155, and I wasn’t recovering between sets. I told myself it was keto flu and it would pass. By day 12 it hadn’t.

Here’s the part that actually changed my mind, and it’s not the fog or the gym numbers — it’s what I found when I pulled the logs afterward. I compared those 16 keto days against the 16 days right before I started: same rough calorie deficit, about 550 a day under maintenance in both stretches. The weight loss rate barely moved — 3.4 pounds on keto versus 3.1 pounds the two and a half weeks prior, eating rice, oats, and fruit right alongside the same protein targets. The carbs weren’t the lever. The deficit was doing all the work, and keto had just made hitting that deficit harder, because cutting out an entire food category at 6pm on a Tuesday when you’re tired is its own kind of decision fatigue.

So why do half my dinners still look keto? Honestly — I just like them. Salmon with garlic butter and roasted vegetables is fast, it’s protein-dense, and it doesn’t leave me hunting for a second plate an hour later. That’s a real advantage, but it’s a food-preference advantage, not a metabolic one. The difference between April-me and now-me isn’t that I’ve relaxed my standards. It’s that I stopped treating rice and bread as a threat that had to be engineered out of every meal.

Two weeks ago my daughter had a birthday party and there was cake — real cake, buttercream, the works. I had a slice, logged it in about ten seconds with a photo, and moved on. There was no negotiation with myself about whether I’d “earned” it or whether it would knock me out of ketosis, because I wasn’t in ketosis to begin with and I wasn’t trying to be. My calories for the day landed about 200 over target. My weight the next morning was up half a pound, which was gone again within two days, same as it always is after a normal high-sodium, high-carb meal. Nothing about that felt like a setback, because nothing was broken to begin with.

I think the keto-or-nothing framing sticks around because it’s a simple story — cut the carbs, unlock the fat loss — and simple stories travel well. But my own numbers said otherwise, and I’ve talked to enough people using ZeroToHero to know my experience wasn’t unusual: the app doesn’t push anyone toward a specific macro split, and the people losing weight steadily are mostly just eating less than they burn, in whatever ratio of foods they can actually stick with for months instead of weeks.

If you’re staring down a keto start date because you think it’s the only path to real results, I’d just ask you to run your own 16-day comparison before you commit to it long-term. Track a normal stretch, then track a strict one, and look at what the deficit alone was already doing. For me, that was the number that mattered — not the grams of carbs on the label.

Garlic butter salmon and roasted asparagus, the repeat anchor dinner Jason logs in ZeroToHero several nights a week

The Same Salmon Dinner, Four Nights a Week — Why Repetition Beat Variety for Me

Somewhere around 6:40 on a Tuesday, Thursday, and usually one more night I couldn’t tell you in advance, you’ll find the same pan in my kitchen: salmon, butter, garlic, a squeeze of lemon, asparagus roasted at 425 until the tips go crispy. Same fish counter, same six-ounce fillets, same nine minutes. I used to think that was a failure of imagination. Now I think it’s the single biggest reason I’ve kept 24 pounds off instead of just losing it once and finding it again.

Here’s what actually happened. Back in May I pulled up three months of logs in ZeroToHero (zerotoherofit.com) and noticed something I didn’t expect: my logging rate on dinners was 71%, but on nights I skipped logging, it was never the salmon. It was always a night I’d decided to “get creative” — a new sheet-pan recipe, something from a food blog, a stir-fry I was inventing as I went. Those nights took longer to cook, dirtied more dishes, and apparently took enough mental energy that logging them felt like one more decision I didn’t have in me. The boring dinner got logged. The exciting one didn’t.

That’s the opposite of what every food blog and cooking show tells you. Variety is supposed to be the reward for eating well. But variety has a cost nobody puts on the label: a decision every single night about what to buy, what to cook, and how to estimate it. I was 232 pounds for a long time in part because I was tired — tired of deciding, not tired of eating vegetables. Removing one decision a day doesn’t sound like much until you multiply it by 365.

So I built an anchor. The salmon dinner is roughly 520 calories and 42 grams of protein for the portion I actually eat — six ounces of fillet, a tablespoon of butter, a full sheet pan of asparagus, nothing measured with a scale anymore because I logged it once, carefully, back in June, and now I just snap a photo and ZeroToHero (zerotoherofit.com) pulls up that same saved meal in about two seconds. No estimating. No guessing whether tonight’s portion matches last week’s. It’s the same answer every time, which means it’s one less place my numbers can drift.

I want to be clear about what this isn’t. It isn’t “eat the same thing forever” or some rigid meal-prep purity test — I’ve written before about why I batch-cook two meals a week instead of seven, and that’s a different problem (time, not decision fatigue). This is one dinner, sometimes two, that I never have to think about, wrapped around four or five nights where I’m actually cooking whatever sounds good. The anchor isn’t the whole week. It’s the floor. When work runs late or the kids have practice and I’m running on fumes, I’m not choosing between takeout and nothing — I already know what I’m making, and it takes eleven minutes.

The numbers back it up more than I expected. In the eight weeks before I built the salmon habit, I averaged 5.1 logged dinners a week. In the eight weeks after, it was 6.4. That’s not a dramatic before-and-after photo kind of change, but it’s the difference between a plateau and steady progress, and it’s exactly the kind of unglamorous fix that doesn’t make it into most weight-loss content because “eat the same dinner a few times a week” doesn’t sell anything.

If you’re the kind of person who feels a little guilty about eating the same thing on repeat, I’d push back on that instinct. The guilt is usually left over from diet culture telling you boring equals deprived. In my experience it’s the opposite — the boring dinner is the one that’s still there for me on the hard nights, which is exactly when I need it to be.

ZeroToHero app graphic: family together at the table

The Bites I Didn’t Count: What My Kids’ Plates Were Costing Me

My daughter’s mac and cheese was gone in four minutes. Mine took eighteen. That fourteen-minute gap is where I lost bites every single night for probably two years before I noticed it.

Back in June my logging was solid — I was hitting 96% of dinners, structured, careful, feeling good about it. But my weight had stalled for eleven days at 211. Nothing in my logged meals explained it. So I did what I always do when the numbers don’t add up: I stopped trusting my memory and actually watched myself eat for a week instead.

Turns out I was finishing my kids’ plates. Not stealing food off them — cleaning up. My 6-year-old leaves four bites of chicken nugget behind, my 9-year-old abandons half a quesadilla the second her friend texts her something, and I was the guy standing at the counter eating the leftovers while I cleared the table. None of it went in ZeroToHero (zerotoherofit.com) because none of it felt like “eating.” It felt like cleanup.

I actually counted for seven dinners straight. Average: 6 unlogged bites a night, roughly 140–180 calories I never touched my phone for. Over a week that’s about 1,100 calories — nearly a full day’s worth of food — vanishing into a category my brain didn’t classify as eating at all.

The fix wasn’t willpower, because willpower doesn’t work on something you don’t register as a decision in the first place. The fix was changing who clears the table. My wife and I already split dinner duty, so I made one rule: whoever cooked doesn’t clear. If I made dinner, she’s on cleanup, and vice versa. That one swap cut my unlogged bites from 6 a night to under 1 within the first week, because I was never standing over the kids’ plates with a fork in a gap moment.

The second thing that actually mattered: I stopped letting “cleaning up” and “eating dinner” happen in the same ten minutes. Now I finish my own plate, log it in the app while it’s still in front of me, and only then start clearing anything. By the time I’m touching my kids’ leftovers, dinner is already logged and closed out in my head. That distinction — closed versus open — did more than any rule about portions ever did.

I want to be straight about this because I built ZeroToHero (zerotoherofit.com) specifically because I kept lying to myself about stuff like this. Not on purpose — I just wasn’t seeing it. I went from 232 pounds down to 208 by photographing what I actually eat instead of estimating it, and the app is good at catching the meals I sit down for. It is not going to catch six absent-minded bites of chicken nugget unless I stop and take a picture of my kid’s plate, which, no offense to the technology, I am not doing at dinner with two kids under ten.

So this one wasn’t a food problem or an app problem. It was a role problem — I’d assigned myself a job (clearing the table) that put me in physical contact with food at the exact moment my guard was down. Once I handed that job to someone else three nights a week, the bites disappeared on their own.

If you’ve got kids, or you’re the one who does dishes, or you always seem to be the last person at the table — check who’s actually finishing the plates in your house. It might not be the kids leaving food behind that’s the problem. It might be you.

ZeroToHero app progress screen showing weight trend line over time

The Scale Jumped Three Pounds Overnight — Here’s Why I Didn’t Panic

Tuesday morning I stepped on the scale and it read 210.8. Sunday it had read 208.0. That’s a 2.8-pound “gain” in two days, and the old me — the guy who was 232 pounds and had quit a hundred diets by the second bad number — would have read that as proof the whole thing was falling apart. Burger and fries Saturday night, so obviously I’d blown it.

I didn’t panic, and I want to walk through the actual math of why, because once I saw it in numbers I couldn’t unsee it.

The math that finally got through to me

A pound of body fat is roughly 3,500 calories. To actually gain 2.8 pounds of fat overnight, I would have needed to eat about 9,800 calories more than I burned in one day. My burger-and-fries night was maybe 1,400 calories over my target. Not even close. So whatever that 2.8 pounds was, it wasn’t fat — it was water, and mostly it was sodium and carbs from the fries doing exactly what sodium and carbs do, which is hold water in your muscles for a day or two.

I pulled up my actual numbers from that week and they tell the story better than I can:

Sunday: 208.0
Monday: 207.6
Tuesday: 210.8
Wednesday: 209.1
Thursday: 207.9
Friday: 206.8

Net change for the week: down 1.2 pounds. If I’d only weighed in on Tuesday, I’d have quit eating carbs for a week out of panic. If I’d only weighed in on Friday, I’d have felt like a genius. Neither number was the truth by itself. The trend across six days was the truth.

Trend weight, not day weight

So here’s what I actually do now: I weigh myself every single morning, same time, right after I wake up and before I eat or drink anything, same scale on the same spot of bathroom floor. Then I ignore that number completely and look at the seven-day rolling average instead. One weigh-in is noise. Seven weigh-ins are a signal.

This sounds obsessive — weighing in daily when I’m telling you not to trust the daily number — but it’s the opposite of obsessive in practice. A single Tuesday scale reading used to be an event that could ruin my whole day. Now it’s just one dot on a line, and the line is what I actually check on. Weighing every day and only judging the average is what took the emotional charge out of the number entirely.

The behavior change was bigger than I expected. I stopped doing the thing where a bad Tuesday number turned into “well, I’ve already blown it, might as well order pizza and start over Monday.” That entire spiral was built on treating one data point like it was the whole verdict. When you know a spike is probably sodium and glycogen and it’ll be gone by Thursday, there’s nothing to spiral about.

I’m the founder of ZeroToHero (zerotoherofit.com), and this is one of the first things I built into it after living through my own Tuesday-morning panic one too many times — every weigh-in gets logged, but the app plots the trend line automatically instead of just showing you yesterday-versus-today. You still see every dot. You’re just not asked to make a decision based on one of them.

If you only take one thing from this: weigh yourself daily under the same conditions for the next two weeks, write every number down, and don’t react to a single one of them. Compare the average of week one to the average of week two. That comparison will tell you more about whether what you’re doing is working than any individual morning ever could.

The Calories I Never Logged Were the Ones I Ate Standing Up

I had eleven straight weeks of what I’d honestly call near-perfect logging. A photo of every meal. Protein target hit most days. Calories inside my range. And for two of those weeks the scale sat at 211 and would not budge.

The maddening part was that I couldn’t find the leak. My logs looked clean — breakfast, lunch, dinner, one afternoon snack. Nothing hidden, nothing fudged.

Then one night I was clearing plates after dinner and caught myself eating the last two chicken tenders off my son’s plate. Standing over the sink. Took maybe eight seconds. And it hit me that I’d done some version of that nearly every night for a month and had never once photographed it.

Here’s the thing about photo logging — and since I built the photo logger, this is me admitting a hole in my own system: you take a picture of food when you sit down with it. Nobody takes a picture of food they eat standing up.

So I counted for nine days

For nine days I did something faintly ridiculous. Every bite that wasn’t part of an actual meal, I photographed. The cheese I ate while grating cheese. The spoon of peanut butter at 10 PM. Three tortilla chips out of the bag while the pan heated up. My daughter’s abandoned mac and cheese. The handful of trail mix from the jar on my desk.

What it added up to:

41 separate eating events that had never been logged
An average of 4.5 per day
Roughly 1,900 calories total
About 210 calories a day

Two hundred and ten calories a day is not a rounding error. That’s a pound every seventeen days. That was my entire deficit — eaten standing up, eight seconds at a time, invisible to a system I designed.

What actually fixed it

My first move was to just stop. I white-knuckled it for four days and it worked exactly as long as white-knuckling ever works, which is until Thursday.

So I swapped the willpower for a rule with a physical step in it: if I want it, it goes on a plate and I sit down with it. That’s the whole rule. Not “don’t eat the chicken tenders.” Put the chicken tenders on a plate, sit in a chair, eat them, photograph them.

Two things happened. First — and this surprised me — roughly 70% of the time I didn’t want the food enough to get a plate out of the cabinet. It was never hunger. It was proximity. Second, the 30% I genuinely did want got logged, which meant my numbers were finally real instead of a flattering fiction.

Three weeks later I was at 208, down from 232 when I started. The stall broke and I never cut a single thing out of a real meal to do it.

I’m the founder of ZeroToHero (zerotoherofit.com), and this blind spot is one I take personally, because the app is a photo logger at its core — which means the same gap applies to anyone using it. Snapping a picture of your dinner is the easy part. The question your data can’t answer for you is what happened between dinner and the dishwasher.

If you’re logging carefully and the scale still won’t move, I’d bet real money it isn’t your meals. Give it nine days of photographing everything you eat while standing up. Don’t try to fix it yet — just look at it. The number is almost always bigger than you’d guess, and more often than not, it’s the entire explanation.

Five Days on the Road, Zero Pounds Gained — I Stopped Needing Willpower and Removed the Decisions Instead

Every work trip used to cost me about three pounds. Not the kind that disappears by Thursday — real ones. I flew to Chicago in March at 219 and stepped on the scale four days later at 222.6. I hadn’t done anything outrageous. No all-you-can-eat anything. I just traveled the way I’d always traveled.

What I told myself before every trip was some version of “I’ll be good.” That’s not a plan. That’s a wish with a suitcase. And it always fell apart the same way: I’d land at 9:40 PM, the hotel restaurant would be closed, and my dinner would be whatever the lobby shop still had behind the glass.

Here’s the part that surprised me when I finally went back and looked at my own logs. My travel dinners weren’t the problem. Dinner on the road averaged within about 80 calories of dinner at home — I sit down, I order a steak and vegetables, I’m fine. The damage was all in the margins. Hotel breakfast buffet. The pastry tray at the 10 AM session. Airport pretzel at 4 PM because I hadn’t eaten since the buffet. Three or four hundred extra calories a day that I never made a decision about. They just happened to me.

So I stopped trying to be disciplined on the road and started removing decisions instead. One rule: I pick breakfast before I leave my house, and I eat the exact same one every morning of the trip. For me it’s three eggs and whatever meat they’ve got, skip the pastry basket, skip the juice. That’s it. I don’t stand at the buffet negotiating with myself at 7 AM in a strange city. I’ve already decided. Five mornings, same plate.

Two things go in my bag now, every time: a bag of beef jerky and a couple scoops of protein powder in a ziplock. Total cost, maybe six bucks. What they actually buy me is the 4 PM decision. If I’m not starving in an airport terminal, I don’t need willpower — there’s nothing to resist.

And I keep logging, which is the part I used to skip entirely when traveling. I’d tell myself I’d catch up when I got home. I never did — and those missing days were exactly the days I most needed to see. Now I just photograph the plate. That’s the whole reason I built ZeroToHero (zerotoherofit.com) the way I did — I needed something that worked when I was tired, in a hotel room, with no scale and no idea what was in the sauce. A photo takes four seconds. Looking up a restaurant’s menu data does not.

Last week I was in Austin for five days. Left at 208.4. Came home at 208.2. Same breakfast five mornings running. I ate barbecue on a Tuesday night and I logged it. Nothing heroic happened — I just didn’t lose ground, which for me is a completely new outcome for a week on the road.

Two honest caveats. I walked a lot more than usual on that trip, and that probably helped more than I can prove. And I wasn’t trying to lose weight in Austin. That’s the actual mindset shift: on the road, flat is a win. Trying to run a deficit while sleeping badly in a hotel and eating food I didn’t cook is how I used to end up abandoning the whole thing by day three.

I’m down from 232 to 208, and the trips used to be where I gave it all back. Turns out I didn’t need more discipline out there. I needed fewer decisions.

I’m Jason Duskin. I built ZeroToHero (zerotoherofit.com), the photo-based food logging app I use myself — so take my enthusiasm for it with that in mind.

ZeroToHero app graphic: structured breaks can boost your weekend progress instead of undoing it

My Weekends Were Erasing My Whole Week — Here’s the Rule That Fixed It

I used to dread Monday mornings on the scale, and it had nothing to do with willpower. For six weeks straight this past spring, the pattern was almost mechanical: by Friday I’d be down 1.5 to 2 pounds from Monday, and by the following Monday, a pound to a pound and a half of that was back. I’d lose the week, then hand most of it right back over 48 hours.

At first I chalked it up to sodium and water — Saturday pizza, a couple of beers, the usual. That’s real, but it doesn’t explain why the same thing kept happening six weeks running while my weekday habits stayed rock solid.

So I went back through two months of my own food logs in ZeroToHero (zerotoherofit.com) and did something I hadn’t bothered to do before: I split my average daily calories by day of the week instead of just looking at the weekly total. Monday through Thursday I was averaging close to my target, somewhere in the 2,000-2,100 range. Friday jumped to around 2,600. Saturday was worse — almost 3,000 on average, and one Saturday hit close to 3,400. Sunday came back down some, but still ran 400-500 over target.

The problem wasn’t that I ate badly on weekends. It’s that I was giving myself permission to treat every single weekend meal as a free pass — Friday dinner out, Saturday brunch, Saturday dinner, sometimes a Sunday brunch too. Four “cheat” meals stacked back to back with nothing logged and no real limit, instead of one planned splurge.

The fix I landed on, and have stuck with for about ten weeks now, is embarrassingly simple: one indulgent meal per weekend, not four. I pick it in advance — usually Saturday dinner, since that’s the one I actually care about, whether it’s a restaurant with my wife or a real backyard cookout. Everything else on Friday, Saturday, and Sunday gets logged and stays close to a normal weekday, even if it’s less structured than a Tuesday lunch at my desk.

I still photograph and log the splurge meal in the app. Not to restrict it — I eat what I want at that meal — but because seeing the number the next morning keeps me honest instead of letting it disappear into “I don’t really know, it was a lot.” That one piece mattered more than I expected. The meals I don’t track are the ones that quietly balloon.

Ten weeks in, my weekend regain has dropped from that 1 to 1.5 pound average down to somewhere around 0.3 to 0.5 pounds most weeks — which is honestly close to normal fluctuation, not a real setback. More importantly, I’m not restarting my week at a deficit anymore. Monday used to feel like damage control. Now it just feels like Monday.

None of this required cutting weekends out or turning into someone who orders dressing on the side. It required admitting that “the weekend” isn’t one meal in my head, it’s four or five, and I was giving all of them the same free pass I only meant to give one. Pick your one meal. Log the rest like they’re Tuesday. That’s the whole rule, and it’s done more for my weight this year than any workout I added.

Couple sharing a meal and drinks at a restaurant table

Why I Stopped Trying to Quit Drinking to Lose Weight

I tried quitting drinking to lose weight three different times. First time was January, obviously. Made it eleven days, white-knuckled a work happy hour, and then had four IPAs in about ninety minutes because I’d spent eleven days thinking about nothing else. Second time I made it three weeks and lost exactly zero pounds, because I replaced the beer calories with an extra bowl of cereal every night before bed. Third time I just quietly gave up and told myself moderation was a myth for people like me.

Turns out moderation wasn’t the myth. My version of it was.

Here’s what nobody told me: a pint of the hazy IPAs I liked was running 230-260 calories, and I was having four or five on a Friday without blinking. That’s over 1,000 calories before I’d eaten a single bite of the wings that came with it. I wasn’t overeating at dinner. I was drinking dinner twice.

The rule that actually worked

I didn’t quit. I capped it at two drinks, and I made the two drinks count. That meant swapping the double IPA for a vodka soda with lime (about 100 calories) or a tequila on the rocks, and treating light beer as the budget option at 100-110 calories instead of the hazy stuff at nearly triple that. Two vodka sodas is 200 calories. Two hazy IPAs is 500. Same two drinks, same night out with the same people, a 300-calorie difference — which, over the four or five times a month I actually go out, is the difference between losing weight and spinning my wheels.

I also stopped pre-gaming the calorie math in my head and started actually logging the drink the second it hit the table, using ZeroToHero (zerotoherofit.com), the app I built specifically because I got tired of guessing. I just snap a photo or type “vodka soda” and it’s done — no mental spreadsheet, no giving up on tracking after drink two because the math got annoying. That’s the actual unlock. It was never about willpower at the bar. It was that logging alcohol felt like a hassle, so I stopped doing it, so I stopped noticing it added up.

The trade I make now

On a night I know I’m having drinks, I eat a lighter lunch — not starving myself, just skipping the bread basket at lunch instead of at dinner, where I actually want it. I bank maybe 200-300 calories earlier in the day and spend them on drink two instead of pretending drink two is free. That’s it. That’s the whole system. It’s not clever, it’s just honest math instead of the story I used to tell myself, which was some version of “I was so good this week, it doesn’t count.”

I’m down to two nights a week where I drink at all, down from basically every night having something, but the two nights I do, I’m not white-knuckling a diet or feeling like I failed the second a drink shows up. My brother’s wedding was in June and I had three drinks and a piece of cake and didn’t think about it again. Old me would’ve either white-knuckled through sober and resentful, or blown the whole week after one drink “ruined it.” Neither of those is sustainable for an entire life. Two drinks, logged, is.

If you’ve tried the dry-January approach and it didn’t stick, you’re not undisciplined. You just built a rule you couldn’t live inside of. Two real drinks you actually enjoy, logged honestly, beats zero drinks for eleven days followed by four in one sitting. I know because I ran that experiment on myself three times before I figured it out.