"I Felt Like 40 at 33": How a Software Engineer Finally Broke the Start-Stop Fitness Cycle
- Alex
- May 15
- 6 min read
He came to me at 95kg, 175cm, and 33 years old.
A software engineer struggling with his fitness.
Not in crisis.
Not in pain.
Just quietly aware that something was wrong.
He'd been gaining weight gradually for years - up and down, never quite reaching his goal of 80-82kg, never fully losing control either.
He played football occasionally with friends and noticed he was the youngest one on the pitch but struggled the most. He worked from home, sat at a desk for 10+ hours a day, and by evening had very little left for anything else.
He'd tried programs before. Always started well. Always stopped.
"I always fail to find a program that fits me," he told me on our first call. "I do well for a couple of weeks, then something happens at work and I stop. And then it's really hard to catch up again."
He wasn't looking for another program. He was looking for a system that would survive real life.
The Pattern That Keeps Most Software Engineers Stuck With Their Fitness Progress
Before getting into what we did, it's worth naming the pattern - because it's not unique to him. I see it constantly with software engineers, developers, and tech professionals.
It goes like this:
Motivation arrives. You find a program. You start strong - three, four, maybe five weeks of consistency. Then a sprint hits. A product launch. A family situation. A week where work expands to fill every available hour.
You miss a session. Then another. You feel guilty. The guilt makes starting again harder. You wait for the right moment to restart properly - and the right moment keeps not arriving.
Three months later you're back to where you started, slightly more convinced that you're "just not someone who sticks to fitness."
This is not a discipline problem.
It's a design problem.
The program wasn't built to survive the life it was supposed to fit into.
What Was Actually Going On
When we dug into his situation, three things stood out.
The program had no disruption protocol.
Every fitness program he'd tried demanded the same output every week regardless of what was happening professionally. There was no built-in answer to the question: what do I do when work gets brutal? So the answer became: nothing. And nothing compounded into stopping.
The nutrition collapsed on weekends.
Monday to Friday, structure carried him. He had a routine - yogurt, fruit, eggs, vegetables - that happened almost automatically because the workday organized the day around it. Weekends were different. Spontaneous, family-focused, lower structure. This is where the invisible calories accumulated and where the weekly progress got undone.
He was under-eating on weekdays and not noticing.
Looking at his caloric intake across the week, he was consistently below 1800 calories on workdays - below what his body needed to support training, recovery, and a cognitively demanding job simultaneously. The tiredness he felt wasn't just work stress. It was his body running on insufficient fuel. The weekday deficit was creating the weekend cravings.
What We Changed
1. A program built around his actual schedule
Two full-body home workouts per week, 30-35 minutes each. No gym required. Exercises he could do in his apartment with minimal equipment.
The key was the disruption protocol: during normal weeks, full sessions with progressive overload. During heavy work weeks, shorter sessions - 20 minutes, reduced volume, maintenance focus. The rule was simple: the session gets shorter, not cancelled.
This one reframe changed everything. He stopped thinking of missed sessions as failure and started thinking of shortened sessions as adaptation. He never fully stopped.
2. Weekend nutrition awareness - not restriction
Rather than adding more tracking during the week when structure was already working, we focused tracking specifically on weekends - the period where the pattern was breaking down.
Just photographing meals on Friday, Saturday, and Sunday. No restriction. Just visibility.
Within two weeks, he could see exactly what was happening. The portions at dinner were significantly larger than he'd realized. The casual snacking while spending time with his daughter added up to several hundred calories he wasn't accounting for. Small adjustments - not dramatic ones - closed the gap.
3. Increasing weekday calories
This sounds counterintuitive when the goal is fat loss, but it was the most impactful change we made.
He was running a caloric deficit that was too aggressive for his actual life - a cognitively demanding job, a young child, training, and a language course he was taking. Increasing his protein intake and overall calories on workdays reduced the fatigue, stabilized his energy through the afternoon, and eliminated the compensatory weekend overeating that had been undoing his weekly progress.
The sweet spot was around 2000-2200 calories on training days. Not a dramatic increase - but enough to support everything he was asking his body to do.
4. Treating movement as the primary lever
One thing most software engineers dramatically underestimate: the calories burned through daily movement outside of structured exercise.
His 10,000 steps on commute days were burning more calories than his training sessions. On work-from-home days, his step count dropped to almost nothing. We made consistent daily walking a non-negotiable - not as "cardio" but as a baseline that his body needed to function and recover properly.
Three days per week of 10,000 steps alongside two training sessions became the minimum effective dose.
The Mindset Shift That Made Everything Work
There was a moment in one of our calls when he described what had changed.
"I don't see the exercise as an extra thing I should do," he said. "It's part of my day that charges me for the rest of it."
This is the shift that separates people who maintain fitness long-term from people who cycle through it perpetually. Fitness stops being something you do when you have time or energy and becomes the thing that creates time and energy.
He also described something else - that on rest days, he felt like something was missing. That he was starting to crave the movement.
When the craving flips from resistance to desire, the habit has formed. At that point, the question changes from "how do I make myself do this" to "how do I fit this in" - which is a much easier problem to solve.
The Results For Just One Month
Starting weight: 97kg.
After consistent application of these changes over several weeks: down to 94.25kg, Aiming toward 80-82kg.
Not dramatic in a 30-day transformation sense. Significant in a sustainable, compounding sense.
More importantly: he was stronger. Pull-ups that required assistance at the start were becoming manageable. Exercises that took 30 minutes were taking 20. He could feel his body changing in ways that the scale doesn't capture.
And he hadn't stopped. Not once, despite a demanding job, a young child, a language course, and a work schedule that would have broken previous attempts.
What This Looks Like for You
If this pattern is familiar - if you've started and stopped more times than you can count, if you know exactly what to do but keep not doing it, if work keeps winning against fitness - the problem is almost certainly not your discipline.
The program wasn't built for your life. The nutrition approach required more cognitive load than you had available. The disruption protocol didn't exist so disruption meant stopping.
The fix is not trying harder. It's building a system that accounts for the actual conditions it has to operate in.
For most software engineers and tech professionals, that means:
Two sessions per week, 30-35 minutes, at home - with a shortened version for heavy work weeks
Protein at every meal, consistent enough to eliminate the hunger that drives compensatory eating
Movement built into the day as a baseline, not added on top as optional extra
Nutrition awareness focused on the specific moments where the pattern breaks down - not blanket tracking that adds cognitive load to an already overloaded system
None of this requires your life to be quieter than it is. It's built for the life you already have.
I work 1:1 online with software engineers, developers, tech leads, and founders who are done with the start-stop cycle. If this resonated - book a free 30-minute call. No pitch. Just a conversation about what's actually going on and what a system that fits your life would look like.
Comments