Why Software Engineers Shouldn't Count Calories (And What Actually Works Instead)

Every few months, a software engineer messages me with some version of the same question: "Should I start counting calories?"

They've read it somewhere.

A Reddit thread, a fitness app, a YouTube video from someone with six-pack abs and apparently unlimited free time.

Count your calories, hit your macros, track everything. It sounds logical. It sounds like a system. And software engineers like systems.

The problem is this one was never built for them.

Where calorie counting actually comes from

Calorie tracking as a standard practice comes from competitive bodybuilding. Bodybuilders need to manipulate their body composition with surgical precision - hitting specific macros to peak at a specific weight on a specific date. For that context, tracking every gram makes complete sense.

It then got picked up by the mainstream fitness industry and presented as the default approach for everyone.

Download MyFitnessPal.

Log everything.

Hit your numbers.

What nobody mentions is that professional bodybuilders typically don't have cognitively demanding full-time jobs.

They train, they eat, they sleep, they recover. Nutrition tracking is essentially part of their job description.

That's not your life.

The cognitive load problem

A software engineer in a mid-level role makes hundreds of decisions a day.

Architecture choices, code reviews, debugging sessions, Slack threads, meetings that could have been emails.

By the time 6pm arrives, the decision-making part of the brain is depleted in a way that has nothing to do with physical tiredness.

This is called decision fatigue, and it's well-documented.

The cognitive resources you use to solve a complex problem are the same ones you'd use to calculate whether your lunch was 480 or 520 calories, and whether that fits your remaining daily budget, and whether you should compensate at dinner.

Adding a tracking system on top of a cognitively exhausting workday doesn't just feel annoying. It actively fails. You either quit within two weeks, or you develop a stressed, obsessive relationship with food that creates more problems than it solves.

I've worked with enough software engineers to know that calorie counting has a near-zero long-term success rate in this population.

Not because they lack discipline - these are people who ship features under pressure and debug production issues at midnight.

Discipline is not the issue. The system is the wrong fit.

What awareness actually looks like

When I started working with Dmitry - a Senior Software Engineer in Berlin, 10-12 hours a day in front of a screen, gaining 1-2kg every year - we didn't open MyFitnessPal.

I asked him to photograph his meals for two weeks and track his weight each morning.

That was it.

No logging.

No calorie targets.

No macro splits.

Just a photo in the app and a number on the scale.

Two weeks of that gave us more useful information than months of strict tracking would have. We could see that his fat intake was high, his protein was low, and daily snacking was adding hundreds of invisible calories he genuinely hadn't noticed. Evening beers alone were a significant contribution he'd completely stopped registering because they'd become background habit.

The fixes that followed were small and specific. Alcohol-free beer in the evenings. Cottage cheese and protein smoothies to hit a rough protein target. More meat at meals, fewer processed snacks.

No restriction.

No spreadsheet.

Just better defaults.

He lost 11.7kg.

The photo method for food tracking and why it works for software engineers

When clients send me photos of their meals through Trainerize, I can give them a rough caloric estimate and immediate feedback. It's not ultra-precise. It doesn't need to be.

The goal isn't laboratory accuracy.

The goal is awareness - understanding broadly what's happening so we can identify the two or three things that are actually causing the problem. In my experience with tech professionals, it's almost always the same short list: protein too low, liquid calories invisible, portion sizes drifted without noticing.

A week of photos surfaces all of that. Then we fix those specific things, and nothing else.

This approach has a much lower cognitive overhead than tracking, it doesn't require an app you have to maintain indefinitely, and it creates the kind of behavioral shift that actually sticks. You start to develop an internal sense of what you're eating without needing external tools to measure it.

The protein anchor

If the photo method feels like too much friction at the start, there's an even simpler entry point: track only protein.

Not calories or fat and carbs. Just protein.

This works because protein is the macro that matters most for body composition. It preserves muscle when you're in a deficit, it has the highest thermic effect of any macronutrient, and it keeps you fuller for longer. When protein is consistently adequate, the other macros tend to self-regulate more naturally.

For most software engineers, a rough daily protein target - say 150-160g for someone at 80kg - is simple enough to track mentally without an app. Chicken breast, eggs, cottage cheese, Greek yogurt, protein shakes. You hit the number, you're done thinking about it.

The caloric math often improves automatically as a side effect, because higher protein intake tends to displace lower-quality calories rather than add to them.

What you don't need

You don't need to know how many calories are in every meal you eat. You don't need a food scale. You don't need to log your dinner before you eat it or feel guilty when you eat something that doesn't have a barcode.

What you need is a brief period of awareness to identify your specific problem, a small number of targeted changes to address it, and a rough protein anchor to keep you oriented.

That's it. Everything else is noise that the fitness industry sells to people who aren't software engineers working 50-hour weeks with families and real lives.

Dmitry didn't transform his life with a strict system. He made three or four small changes based on what the photos showed, built a workout habit that took 28 minutes twice a week, and lost 11.7kg. More importantly, when he stopped working with me for a while - life happened, a surgery, schedule changes, a long holiday in Italy - he didn't gain it all back. The system had become internalized.

That's what sustainable nutrition actually looks like for this population.

If you want to understand what your specific two or three things are, book a free 30-minute call and we'll find them.