What protocol are you running?

Fitness & Performance · Dev Edition

HIIT:
Stress Testing
Your Hardware

You wouldn't benchmark a server at 40% load. Why would you train that way? HIIT is what happens when you run your body at maximum throughput — on purpose.

---

// what it is

Not cardio. A protocol.

High Intensity Interval Training is exactly what it sounds like — alternating periods of maximum effort with short recovery windows, repeated until the session is done. But calling it "cardio" undersells what's actually happening. HIIT is a structured stress test. You're deliberately pushing the system past its comfortable operating range, forcing adaptation responses that steady-state exercise never triggers.

Traditional cardio runs your cardiovascular system at moderate load for an extended period. HIIT spikes you to near-max, lets you partially recover, then spikes again. The result is a completely different set of adaptations — and a workout that takes a fraction of the time.

WORK :20

REST :10

WORK :20

REST :10

WORK :20

REST :10

WORK :20

Mental model: steady-state cardio is a long-running process at constant CPU usage. HIIT is a burst workload — spike to 100%, throttle back, spike again. The scheduler is your rest timer.

---

// the mechanism

What's actually happening under the hood

During a work interval, you blow past your aerobic threshold and enter anaerobic territory. Your muscles can't get oxygen fast enough, so they switch to anaerobic glycolysis — burning glucose without oxygen to produce ATP. Fast, but dirty. The byproduct is lactate, and hydrogen ions that cause that burning sensation in your legs.

The rest interval is where the interesting work happens. Your body scrambles to clear lactate, restore oxygen, and bring your heart rate back down before the next spike. It never fully succeeds — each interval you start a little more depleted. That's the point. The incomplete recovery is the stimulus.

# hiit session loop

def hiit_session(rounds=8, work=20, rest=10):
  oxygen_debt = 0
  lactate = 0

  for round in range(rounds):
    # work interval — anaerobic zone
    lactate += anaerobic_output(duration=work)
    oxygen_debt += work * 0.8     # debt accumulates

    # rest interval — partial recovery only
    lactate -= clearance_rate(duration=rest)
    # debt never fully clears between rounds

  return oxygen_debt              # EPOC — paid back post-workout

---

// EPOC

The after-burn is real — and it's a background process

Here's where HIIT earns its reputation. After the session ends, your body has a massive oxygen debt to repay — technically called Excess Post-exercise Oxygen Consumption (EPOC). Your metabolism stays elevated for hours as it clears lactate, restores ATP and creatine phosphate, lowers body temperature, and repairs muscle tissue.

You're burning calories at an elevated rate while doing nothing. It's a background process kicked off by the session and running long after you've left the gym. Steady-state cardio produces minimal EPOC. HIIT produces significant EPOC because the metabolic disruption is orders of magnitude larger.

VO2 max gains

Cardiovascular ceiling rises faster than with steady-state training.

Mitochondrial density

More mitochondria per cell. Better energy production at any intensity.

Insulin sensitivity

Muscles become more efficient at absorbing glucose. Metabolic health improves.

EPOC

Elevated metabolism for 12–24hr post-session. The afterburn is a real background job.

---

// the protocol

Picking the right ratio

Work-to-rest ratio determines what system you're training. A 1:1 ratio (20 on, 20 off) hammers your cardiovascular system. A 1:2 ratio (20 on, 40 off) lets you go harder per interval, targeting peak power output. A 1:4 ratio pushes into true sprint territory — maximal explosiveness each round.

The most common HIIT protocol you've probably heard of — Tabata — runs 20 seconds on, 10 seconds off for 8 rounds. That's 4 minutes of work that produces measurable VO2 max improvements comparable to much longer steady-state sessions. The research on it is solid. It's also absolutely brutal, which is why most people don't actually do it at true maximum effort.

Warm up (5min)

→

Sprint interval

→

Partial recovery

→

Repeat 6–10x

→

Cool down

→

EPOC runs...

---

// warnings

Don't skip error handling

HIIT has a higher injury risk than steady-state because you're operating at or near max output. Poor form at high intensity is how you get hurt. The fix is the same as it is in code: don't optimize before you have correctness. Get your movement patterns right at lower intensity first, then add the sprint.

Recovery also matters more than most people think. Two to three HIIT sessions a week is plenty for most people — the adaptation happens during rest, not during the session. Stack too many sessions without recovery and you're not training, you're accumulating technical debt in your connective tissue. It pays out slowly, then all at once.

Frequency rule: HIIT sessions are expensive system calls. Two or three per week is the right rate limit. More than that and you're not recovering between calls — you're just crashing the process slowly.

Brenden · 2026 EPOC.resolve();