Geebs Coaching

Geebs coaching guide

Workout Plan for Programmers | Bodyweight + Lifting

3-day workout plan for programmers and developers: bodyweight and lifting exercises for desk workers, simple progression, movement habits for all-day sitting.

In this guide

  • Programmers need low-friction training
  • Run sessions in order, not by perfect weekdays
  • Progress like an engineer, but do not overbuild

Programmers need low-friction training

A workout plan for programmers has to respect the way programming work actually feels. Deep work, context switching, production issues, and long seated blocks all drain bandwidth before the gym even starts.

The answer is not a complicated six-day split. The best default is three focused lifting sessions, daily walking, and nutrition targets simple enough to execute after a long day at the laptop.

You can make the plan more advanced later. First, it has to be repeatable.

Run sessions in order, not by perfect weekdays

Most programmers miss workouts because the calendar changes. Treat the plan as Session 1, Session 2, and Session 3 instead of Monday, Wednesday, and Friday.

If a deployment ruins Wednesday, the next workout is still Session 2. You did not break the plan; you shifted it.

That small change keeps the week from becoming all-or-nothing, which is where most busy professionals lose consistency.

Progress like an engineer, but do not overbuild

Track a few main lifts, use a rep range, and add weight when the top of the range is clean. That is enough signal for months.

Do not rewrite the whole program every time a lift feels off. Treat each week as data: sleep, steps, protein, waist trend, bodyweight, and performance.

Coaching helps because it gives the system a decision-maker. You still learn the why, but you stop debugging your body alone.

What the desk-work evidence can tell you

The training plan above is deliberately simple. That matters when your job keeps you in one position for long stretches and your attention is already spent by the time work ends. The studies below do not test this exact three-day lifting plan. They do give useful context for why it is worth building movement into a workday instead of treating it as an optional extra.

Bontrup and colleagues (2019) looked at sitting behaviour and back pain in 64 call-centre employees, using a textile pressure mat across 400 hours of sitting and questionnaires about acute and chronic low back pain (PMID 31422243). Seventy-five percent of the participants reported some level of acute or chronic back pain. The people with chronic low back pain showed a possible trend toward more static sitting than participants without pain, but the comparison was not a reliable difference. The study found a stronger association between sitting behaviour and chronic low back pain than with acute pain or disability.

That is a useful reminder to avoid a false promise: no workout can guarantee that desk work will not hurt, and this study cannot prove that static sitting caused anyone's pain. It does suggest that changing position during a long day is worth treating as a practical part of the plan. A short walk, a few bodyweight movements, or simply leaving the desk between work blocks gives you a repeatable break from staying still. The goal is not to turn every break into a workout. It is to make movement normal enough that a packed day does not erase it.

Landais and colleagues (2022) asked office workers how they viewed physical activity and sitting (PMID 35354447). Their qualitative study identified six themes. Workers' beliefs about physical activity's health effects were specific, while their beliefs about sitting were more superficial. Health mattered to participants, but social and work-related values sometimes took priority. Barriers came from both internal and external factors, while supportive factors included information and support in the social and physical environment.

For a programmer, that fits the real problem better than a lecture about motivation. You may know that movement matters and still have a release, a bug, or a meeting-heavy day take over. Build the plan around the conditions you actually have. Keep shoes by the door, make the first exercise easy to start, choose sessions in order rather than attaching them to perfect weekdays, and use a calendar reminder if that helps. Those are not magic fixes. They are ways to make the physical and work environment support the choice you already want to make.

Bailey (2021) reviewed workplace sitting, its health implications, and workplace interventions (PMID 33710270). The review describes office workers as highly sedentary and reports that individual, organisational, and environmental approaches can reduce workplace sitting. It also makes an important distinction: evidence for effects on health outcomes from workplace sitting interventions was inconsistent. Bailey notes that combinations of approaches may be most effective at reducing sitting, while long-term health and cost-effectiveness still need more study.

Use that nuance when you set expectations. A walking pad, standing option, reminder, or lunchtime walk can be useful, but none needs to carry the whole job. Pair one workday movement habit with your lifting sessions and make both easy to resume after a disrupted week. If a workday becomes unusually busy, do the smallest version you can complete, then return to Session 1, 2, or 3 when you have time. Consistency comes from having a plan that survives ordinary interruptions.

Keep the decision small enough to make before the day gets away from you. Decide which lift comes first, where you will walk, and what counts as a completed short break. Then let the plan be flexible about timing. The point is not a perfect streak or a heroic catch-up session after every missed workout. It is a simple set of defaults that fits beside the work you already have. When your schedule loosens, continue with the next session rather than trying to repay the workouts you missed.

Honest limits

These papers focus on office and call-centre workers, not programmers specifically, and they do not compare bodyweight exercises with lifting or test the exact schedule on this page. Bontrup's study reports a relationship between sitting behaviour and pain; it does not establish that one caused the other. Landais reported workers' perspectives, not a training result. Bailey reviewed workplace interventions and found that health outcomes were inconsistent. Treat the evidence as a reason to make regular movement easier in a desk-based life, not as a promise about pain, fitness, or results.

FAQ

Quick questions

What are the best bodyweight exercises for developers?

The best bodyweight exercises for developers are push-ups, bodyweight squats and split squats, glute bridges, doorframe or table rows, planks, and wall sits. They counter long sitting blocks, need no equipment, and fit between meetings. Use them as movement snacks on non-lifting days, not as a replacement for the three weekly strength sessions.

What is the best workout plan for programmers?

A three-day resistance-training plan is the best default for many programmers. It gives enough frequency to build strength and muscle while leaving recovery room for long seated work and mentally demanding days.

Should programmers train every day?

Most do not need to lift every day. Three focused lifting days plus daily walking or movement breaks is a better starting point than a high-frequency plan that collapses during busy work weeks.

How do programmers stay fit while sitting all day?

Use strength training as the anchor, then add daily movement defaults: short walks, post-meal steps, walking-pad blocks, or scheduled breaks. Nutrition and protein targets handle the body-composition side.

Keep going

Ready to build your custom plan?

Apply for 1:1 online coaching with Kris. Qualified applicants get direct access to Kris's calendar.

Written by Kris, NASM-CPT. Last updated 2026-06-12. 6 min read.