Ojaswi Athghara | Breaking the Sedentary Cycle: A Developer's Journey to Fitness at 27

Breaking the Sedentary Cycle: A Developer's Journey to Fitness at 27

The Wake-Up Call: Debug Your Health Before It Crashes

I was 27, sitting at my desk for the 12th hour that day, debugging a production issue. My back hurt. My shoulders were tight. My energy was at zero despite three cups of coffee.

The bug? Fixed. The cost? My health was compiling errors I'd been ignoring for years.

That night, I made a decision: if I can dedicate 12 hours to fixing code, I can dedicate 1 hour to fixing my body.

This is my journey from sedentary developer to someone who actually exercises. No overnight transformation, no miracle routine—just a developer learning to optimize his body like he optimizes his code.

The Developer's Dilemma: Sedentary Lifestyle

My Typical Day (Before)

6:00 AM: Wake up, check emails on phone
7:00 AM: Sit at desk, morning standup
8:00 AM - 1:00 PM: Coding (sitting)
1:00 PM: Lunch at desk (still sitting)
2:00 PM - 7:00 PM: More coding (sitting)
7:00 PM: Dinner (sitting)
8:00 PM - 11:00 PM: Side projects or gaming (sitting)
11:00 PM: Sleep

Total sitting: 14+ hours
Total exercise: 0 minutes
Steps per day: Maybe 2,000 if I was lucky

The Health Compiler Warnings I Ignored

Like ignoring TypeScript errors, I ignored health warnings:

Back pain: "It's just from sitting, I'll adjust my chair"
Weight gain: "I'll start working out next month"
Low energy: "Just need more coffee"
Poor posture: "Slouching is my natural state"
Brain fog: "It's just a tough problem I'm working on"

These weren't warnings anymore. They were errors. Time to debug.

Why I Finally Started: The Developer's Perspective

1. Code Performance Requires Human Performance

I noticed a pattern:

9:00 AM: Peak productivity, solving complex problems
2:00 PM: Slower, making silly mistakes
6:00 PM: Brain feels like it's running on a Pentium II

The bottleneck wasn't my code. It was my body.

The realization: You can't optimize your code if you haven't optimized yourself.

2. The Long-Term Tech Debt of Poor Health

In coding, technical debt compounds. In health, it's the same:

Year 1: "I'll start exercising next week"
Year 2: "I should really get healthy"
Year 3: "I need to do something about this"
Year 5: "Why does everything hurt?"
Year 10: Health issues that could have been prevented

At 27, I was already feeling the effects. Time to refactor my lifestyle.

3. Debugging is Harder with Brain Fog

Ever try to debug complex code when you're tired, unfocused, and your brain feels sluggish?

Exercise changed my cognitive function:

Before: 4-5 hours of peak productivity
After: 7-8 hours of sharp focus
Problem-solving: Clearer, faster decisions
Code reviews: Better attention to detail

4. Sitting is the Developer's Silent Killer

The statistics scared me:

Sitting 8+ hours daily increases health risks dramatically
Developers have higher rates of back problems, obesity, and cardiovascular issues
Poor posture leads to chronic pain

I was speedrunning health problems.

Choosing the Push-Pull-Legs Split: The Developer's Workout System

As a developer, I needed a system. Not chaos. Push-Pull-Legs (PPL) is like a well-architected codebase:

Why PPL Works for Developers

1. Logical Structure

Push Day:  Chest, Shoulders, Triceps
Pull Day:  Back, Biceps
Leg Day:   Quads, Hamstrings, Calves, Glutes

Clean separation of concerns. Each muscle group gets focused attention.

2. Scalable and Flexible

Beginner:  3 days/week (Push, Pull, Legs)
Advanced:  6 days/week (Push, Pull, Legs, Push, Pull, Legs)

Start small, scale as you grow. Like building an MVP before the full product.

3. Balanced Development

No muscle group is neglected. Like ensuring all parts of your codebase get attention.

4. Recovery Time Built-In

Each muscle group gets 48-72 hours recovery. Your muscles compile in the background while you work on other areas.

My PPL Schedule (As a Working Developer)

Monday: Push Day

Morning: 6:30 AM - 7:30 AM (before work)
Exercises: Bench press, shoulder press, tricep dips

Tuesday: Pull Day

Morning: 6:30 AM - 7:30 AM
Exercises: Pull-ups, rows, bicep curls

Wednesday: Rest or Light Cardio

Evening walk after work

Thursday: Leg Day

Morning: 6:30 AM - 7:30 AM
Exercises: Squats, lunges, calf raises

Friday: Rest

Focus on work deadlines

Saturday: Push Day (repeat)

Morning: 8:00 AM - 9:00 AM

Sunday: Pull Day or Rest

Depends on energy levels

Key insight: Morning workouts meant no mental decision fatigue. It's done before my brain wakes up enough to make excuses.

Week 1: The Initialization Phase

Day 1: Push Day (The Reality Check)

What I thought would happen:

Go to gym
Lift heavy weights
Feel like Thor

What actually happened:

Couldn't even do a proper push-up
Form was terrible
Sore for 3 days
Questioned all life choices

// My first workout
const pushDay = {
    benchPress: '10kg bar' // Couldn't even lift the standard 20kg bar
    pushUps: 5, // Modified, on knees
    shoulderPress: '2kg dumbbells',
    status: 'EXTREMELY_HUMBLING'
};

Lesson learned: Start with embarrassingly light weights. Form over ego.

The Soreness (DOMS - Delayed Onset Muscle Soreness)

Day 2 after first workout:

Couldn't lift arms above head
Walking up stairs was an achievement
Typing was painful
Sitting down required planning

The developer parallel: Like refactoring a large codebase. It hurts at first, but it gets better.

Week 1 Challenges

1. Time Management

Before: Sleep until 7:30 AM, rush to start work at 9 AM
After:  Wake up at 6:00 AM, gym 6:30-7:30, start work at 9 AM

Required going to bed earlier. My late-night coding sessions had to be scheduled differently.

2. Energy Levels

First week, I was EXHAUSTED. Needed more sleep. Productivity temporarily dropped.

3. Motivation

Wanted to quit multiple times. The soreness made me question everything.

What kept me going: Treating it like a sprint. "Just finish this week."

Month 1: The MVP (Minimum Viable Physique)

The Routine Starts to Compile

After 4 weeks:

Form improved significantly
Soreness reduced
Could actually lift respectable weights
Started seeing slight changes

// Progress tracking (developer style)
const month1Progress = {
    benchPress: '10kg -> 25kg',
    pushUps: '5 (knee) -> 15 (full)',
    bodyWeight: '82kg -> 80kg',
    energy: 'constantly tired -> noticeably better',
    productivity: 'down 20% -> back to baseline + 10%',
};

The Unexpected Developer Benefits

1. Better Problem-Solving

Working out cleared my mind. Solutions to coding problems often came during or after gym sessions.

2. Improved Sleep

Before: Fall asleep at 1 AM, wake up groggy
After:  Fall asleep at 11 PM, wake up refreshed

Better sleep = better code.

3. More Energy Throughout the Day

The afternoon slump disappeared. My energy was consistent.

4. Reduced Stress

Deadlines felt less overwhelming. Bad code reviews didn't ruin my day. Lifting heavy things made work problems feel lighter.

The Technical Details: My PPL Routine

Push Day (Chest, Shoulders, Triceps)

Warm-up:
- 5 minutes light cardio
- Arm circles and stretches

Main Exercises:
1. Bench Press: 4 sets x 8-10 reps
2. Overhead Press: 3 sets x 10-12 reps
3. Incline Dumbbell Press: 3 sets x 10-12 reps
4. Lateral Raises: 3 sets x 12-15 reps
5. Tricep Dips: 3 sets x 10-12 reps
6. Tricep Pushdowns: 3 sets x 12-15 reps

Cool-down:
- Stretching for 5-10 minutes

Total time: 50-60 minutes

Pull Day (Back, Biceps)

Warm-up:
- 5 minutes light cardio
- Shoulder rotations

Main Exercises:
1. Pull-ups or Lat Pulldowns: 4 sets x 8-10 reps
2. Barbell Rows: 3 sets x 10-12 reps
3. Dumbbell Rows: 3 sets x 10-12 reps
4. Face Pulls: 3 sets x 12-15 reps
5. Bicep Curls: 3 sets x 10-12 reps
6. Hammer Curls: 3 sets x 10-12 reps

Cool-down:
- Stretching

Total time: 50-60 minutes

Leg Day (Quads, Hamstrings, Glutes, Calves)

Warm-up:
- 5 minutes light cardio
- Leg swings and stretches

Main Exercises:
1. Squats: 4 sets x 8-10 reps
2. Romanian Deadlifts: 3 sets x 10-12 reps
3. Leg Press: 3 sets x 12-15 reps
4. Lunges: 3 sets x 10-12 reps per leg
5. Leg Curls: 3 sets x 12-15 reps
6. Calf Raises: 4 sets x 15-20 reps

Cool-down:
- Stretching (especially hip flexors)

Total time: 50-60 minutes

Developer tip: I tracked everything in a notes app. Sets, reps, weight. Progress is measurable when you track it.

Balancing Code and Gains: Time Management

My Daily Schedule (After)

6:00 AM: Wake up, pre-workout meal (banana + coffee)
6:30 AM - 7:30 AM: Gym
7:45 AM: Shower, breakfast
9:00 AM: Start work (energized!)
12:30 PM: Lunch (proper meal, not at desk)
1:00 PM - 6:00 PM: Work
6:30 PM: Dinner
7:00 PM - 10:00 PM: Side projects or learning
10:30 PM: Wind down
11:00 PM: Sleep

Total sitting: 8-9 hours (much better!)
Total exercise: 60 minutes
Steps per day: 6,000-8,000

How I Made Time

What I cut:

❌ Late-night gaming (mostly)
❌ Endless scrolling on social media
❌ "I'll just watch one more episode"
❌ Sleeping in until work starts

What I gained:

✅ 1 hour of focused exercise
✅ Better sleep schedule
✅ More energy for coding
✅ Clearer mind for problem-solving

The math:

const timeInvested = 7 hours/week; // ~1 hour x 7 days
const productivityGain = 10-15%; // More focused hours
const healthBenefits = 'PRICELESS';

// ROI is positive

The Challenges Developer Face (And How I Solved Them)

Challenge 1: "I Don't Have Time"

Solution: You have time. You're choosing to spend it elsewhere.

I was spending 2-3 hours/day on YouTube and Reddit. Cutting that to 1 hour freed up time for gym.

Challenge 2: "I'm Too Tired After Work"

Solution: Work out in the morning.

Evening willpower is depleted. Morning you hasn't made any decisions yet. Morning workouts happen.

Challenge 3: "Gym is Intimidating"

Solution: Everyone started somewhere.

That buff guy doing heavy squats? He was once lifting the empty bar too. Nobody cares what you're lifting.

Challenge 4: "What if I'm Sore and Can't Work?"

Solution: That's why PPL splits work.

Upper body sore? It's leg day. Legs sore? It's push day. You're never completely out of commission.

Challenge 5: "I Don't Know What I'm Doing"

Solution: Research, ask for help, hire a trainer for a few sessions.

As developers, we're good at learning. Apply those same skills to fitness.

The Productivity Boost: Unexpected Side Effects

Code Quality Improved

// Before exercise
function calculateTotal(items) {
    let total = 0;
    for(let i = 0; i < items.length; i++) {
        total = total + items[i].price; // Brain fog code
    }
    return total;
}

// After exercise
const calculateTotal = (items) => 
    items.reduce((sum, item) => sum + item.price, 0);
// Clear, concise, functional

My code became cleaner. My thinking became clearer.

Focus and Deep Work

Before: Distracted every 15-20 minutes
After: Can focus for 90-120 minute blocks

Better Sleep = Better Debugging

Complex bugs that seemed impossible at 11 PM became trivial at 9 AM after good sleep and a morning workout.

Stress Management

Production bug at 3 PM?
Before: Panic, stress, make hasty decisions
After: Stay calm, think clearly, solve systematically

Month 3: The Refactored Version of Me

Physical Changes

Lost 6 kg of fat
Gained visible muscle definition
Back pain: 90% reduced
Posture: significantly better
Energy: consistent throughout day

Mental Changes

Clearer thinking
Better focus
Improved mood
Reduced anxiety
More confidence

Career Impact

Better code reviews (more patient, thorough)
Improved system design (clearer thinking)
More productive pair programming
Better at explaining complex concepts
Promoted at work (correlation? maybe. causation? who knows.)

Lessons for Developers Starting Fitness

1. Start Small (MVP Approach)

// Don't do this
const goals = {
    gymFrequency: '7 days/week',
    duration: '2 hours/session',
    diet: 'perfect meal prep',
    results: 'six-pack in 1 month'
};
// This will fail

// Do this
const goals = {
    gymFrequency: '3 days/week',
    duration: '45 minutes',
    diet: 'slightly better choices',
    results: 'feel better, sleep better'
};
// This is sustainable

2. Track Everything (Like Metrics)

As developers, we love data:

Track weights lifted
Track reps and sets
Track how you feel
Track sleep quality
Track energy levels

Data shows progress when motivation is low.

3. Consistency > Intensity

const inconsistentIntense = {
    mondayGym: 'BEAST MODE - 2 hours',
    tuesday: 'too sore, skip',
    wednesday: 'still sore, skip',
    thursday: 'lost momentum, skip',
    result: 'gave up'
};

const consistentModerate = {
    monday: '45 min workout',
    tuesday: 'rest',
    wednesday: '45 min workout',
    thursday: 'rest',
    friday: '45 min workout',
    result: 'still going strong'
};

4. Treat It Like a Standup Meeting

You don't skip standups because you "don't feel like it." Same with gym.

My rule: Only skip if actually sick. Not "I'm tired" sick. Actually sick.

5. The Compound Effect

const dailyImprovement = 1.01; // 1% better each day
const days = 365;
const result = Math.pow(dailyImprovement, days);
// Result: 37.78x better after a year

Small improvements compound. Like learning to code. First week is hard. After months, you're building full applications.

The Developer's Nutrition Guide (Simplified)

I'm not a nutritionist, but here's what worked:

Before (Bad)

const diet = {
    breakfast: 'coffee',
    lunch: 'pizza at desk',
    snacks: ['chips', 'energy drinks', 'more coffee'],
    dinner: 'takeout',
    result: 'low energy, weight gain'
};

After (Better)

const diet = {
    breakfast: 'eggs + oatmeal + fruit',
    lunch: 'chicken + rice + vegetables',
    snacks: ['protein shake', 'nuts', 'fruit'],
    dinner: 'fish/meat + vegetables',
    water: '3 liters/day',
    result: 'sustained energy, better recovery'
};

Key changes:

More protein (for muscle recovery)
More water (for everything)
More whole foods, less processed
Meal prep on Sundays (like batch processing)

Common Developer Excuses (And Why They're Bugs)

"I'll Start Next Month"

if (readyToStart === 'next month') {
    // This condition is never true
    // Next month becomes "next month" again
}

// Better:
const startDate = new Date();
console.log('Starting today');

"I Need to Research More First"

Analysis paralysis. You don't need the perfect routine. You need a routine.

"I Can't Afford a Gym"

Bodyweight exercises are free. Push-ups, squats, planks—no equipment needed.

"I'm Not Athletic"

Neither was I. Neither are most developers. That's the point of starting.

Tools and Resources for Developer Fitness

Apps I Use

Strong: Workout tracking (like Git for exercises)
MyFitnessPal: Calorie tracking (debugging nutrition)
Sleep Cycle: Sleep tracking (monitor recovery)

Learning Resources

r/Fitness - Great community
r/bodyweightfitness - No gym needed
StrongLifts 5x5 - Beginner program

YouTube Channels

Jeff Nippard - Science-based
Athlean-X - Form and technique

The Future: Continuous Integration for Health

This isn't a sprint. It's continuous integration.

My Goals (Next 6 Months)

Maintain consistency (3-4 workouts/week minimum)
Lose another 5 kg of fat
Gain more muscle
Maybe try rock climbing (developers love problem-solving, right?)
Run a 5K without dying

The Long Game

At 27, I'm not trying to become Mr. Olympia. I'm trying to:

Code without pain at 37
Have energy to build side projects at 47
Still be active at 67

Conclusion: Optimize Your Runtime, Not Just Your Code

The most important system you maintain isn't your codebase. It's your body.

You can refactor code. You can migrate databases. You can rewrite entire applications.

You can't rewrite your health from scratch. You have to maintain it incrementally.

If I could tell my 25-year-old developer self one thing:

"The hour you spend at the gym will give you 10 more productive hours at your desk. Not immediately. But over time."

To fellow developers considering fitness:

You don't need to be perfect. You don't need the best gym. You don't need the perfect routine.

You just need to start.

Pick a day. This week. Go to a gym. Lift something. Do push-ups. Walk for 30 minutes.

Your future self (and your code) will thank you.

If you're a developer starting your fitness journey or have tips to share, I'd love to hear from you! Connect with me on Twitter or LinkedIn and let's share our progress!

Support My Work

If this guide helped you with this topic, I'd really appreciate your support! Creating comprehensive, free content like this takes significant time and effort. Your support helps me continue sharing knowledge and creating more helpful resources for developers.

☕ Buy me a coffee - Every contribution, big or small, means the world to me and keeps me motivated to create more content!

Photo by Samuel Girven on Unsplash

Related Blogs