Going to the gym is often viewed purely as physical exercise, but for me, it has always been the ultimate reset button and mental training ground.

In the gym, there is one rule that dictates whether you grow or stay the same: Progressive Overload.

You cannot add 50 lbs to your bench press overnight. If you try, you either fail the rep or injure yourself. Progress comes from adding 2.5 lbs each week, squeezing out one extra clean repetition, or improving movement efficiency under the bar.

Parallels to Software Engineering

In engineering, we frequently see people burn out attempting massive leaps:

• Rewriting entire codebases from scratch
• Trying to master three completely different programming paradigms simultaneously
• Over-optimizing architectures before understanding the core problem

When you apply the progressive overload framework:

1. Consistency over intensity: Hitting your gym sessions 4 days a week every single month beats destroying yourself once every two weeks. Similarly, small, consistent commits and refactors beat messy marathon crunch sessions.
2. Track the metrics: You cannot manage what you don’t track. In lifting, that is weight, sets, and RPE. In software, that is latency, test coverage, memory, and uptime.
3. Recovery is where growth happens: Muscle doesn’t grow in the gym; it grows when resting and sleeping. Clean thinking happens when you step away from the monitor and let your subconscious connect the dots.

Lifting heavy weights keeps me grounded, humble, and physically energized to tackle complex software problems.