// beyond code

Iron &
Discipline.

Bodybuilding is my counterweight to the screen. The habits it demands — progressive overload, consistency, form-first execution — are the same ones I bring to every system I build. 15+ years under the iron, and it shows up in how I work.

15+
Years training
5–6
Days / week
∞
Consistency
Stanobi - fitness
The Journey

Progress compounds

Long-term progression over quick results — a marathon, not a sprint. The payoff is slow, then obvious. Same as a codebase you tend to every day.

Before Before
After After
The Approach

Training & mindset

Training Philosophy

  • Progressive overload as a core principle — same mindset as iterative system optimisation
  • Compound movement focus: squat, bench, deadlift, overhead press, barbell rows
  • Structured programming: push/pull/legs splits, periodisation, and deload cycles
  • Form-first approach: technique over ego, consistent with debugging methodology

Discipline & Consistency

  • Training 5–6 days a week — same reliability as production uptime commitments
  • Nutrition tracking and meal prep for sustained muscle growth and recovery
  • Sleep optimisation and recovery protocols as part of the training cycle
  • Long-term progression over quick results — a marathon, not a sprint

Mindset

  • The gym is where I recalibrate — problem-solving clarity after a heavy session
  • Same principles apply: consistency compounds, discipline beats motivation, form matters
  • Goal-setting: measurable milestones, tracked progress, regular programme adjustments
  • Balance — the discipline of fitness carries directly into the discipline of engineering

Why this belongs on a developer's site.

I don't separate the two. The gym taught me the things that make me good at shipping software: show up when you don't feel like it, add load gradually, respect the fundamentals, and trust that small reps compound into something big. Here's how the one maps onto the other.

Progressive overload
→
Ship in small increments; let systems grow under steadily increasing load.
Form over ego
→
Clean, correct execution beats flashy shortcuts — the same as writing maintainable code.
Show up daily
→
Consistency beats intensity. Production uptime is a training streak that never breaks.
Track everything
→
Measured progress — lifts, macros, sleep — mirrors metrics, logs, and monitoring.
Deload & recover
→
Rest is part of the plan. Sustainable pace ships more than burnout ever will.
Break plateaus
→
When progress stalls, change the variable — tempo, intensity, or approach. Debug the block.