Skip to main content

My exercise routine

Some people have asked me about my exercise routine, so I decided to post it. First, this is not a routine from a book or infomercial - I developed it myself after deciding my goals and reading up on fitness and exercise science. I'm constantly adjusting it, and still trying to figure out what works best. This probably is not for you, and besides: Don't take health advice from engineers.

Now that that's all said and done, let's start with the goals. I wanted to create an exercise program that would improve total body fitness. Specifically, I wanted to get stronger (but not focusing on hypertrophy), more powerful, and most importantly, more aerobically fit, as I felt that was my weakest point.

The problem is that strength and cardio fitness seem to be at nearly complete odds with one another. Every see how gaunt marathon runners are? Have you ever seen a bodybuilder ride the Tour de France? I noticed this quickly myself in terms of mixing workouts: if I did a hard leg strength day, then my legs hurt too much to run or bike the next day. And conversely, if I did a long cardio day, my legs felt like rubber and couldn't do strength or power the next day.

In any case, here is my current program, after 5 weeks of tweaking:
Sunday: Long, low-intensity cardio (e.g., two hour zone 2 bike ride).
Monday: Rest or yoga.
Tuesday: Strength circuits.
Wednesday: Running intervals on the treadmill.
Thursday: Low-intensity recovery cardio (e.g., one hour zone 2 bike ride)
Friday: Strength circuits.
Saturday: Rest day.

So far, this routine creates the best balance of strength and cardio training for me. Wednesday and Friday are the toughest days, mainly because running intervals are my VO2max training, in addition to following a strength day which almost always has leg exercises. And Friday is the fourth workout in a row, but I'm willing to push hard because I know Saturday is a rest day.

The two "zone 2" bike rides are my attempt to build an aerobic "base", and are probably also good for lactic acid threshold training. I usually keep my heart rate between 125 and 140 for these days. Sometimes I get bored and push hard (160-170) for 15 minutes or so.

I've chosen a circuit-based strength workout that usually consists of three different supersets (two different exercises), three sets each, resting 60 seconds between rounds. I try to focus on larger muscle groups, and since I only do strength twice a week, I try to hit all the major muscle groups each time. I do a different workout Tuesday and Friday, and try to swap in at least half new exercises every week. The circuit aspect and short rests mean that these are tough cardio workouts, too. For warmup and cooldown, I do very low-intensity cardio, usually 10 minutes each.

About half the days I use foam rollers after I finish, and I've noticed that this speeds recovery, especially for iliotibial and quad soreness.

Since beginning this program, I've noticed dramatic improvements in my aerobic capacity. This is noticeable on the intervals, which have been improving every week (I also have to work harder to get a stitch, which confirms my belief that I used to get them from overworking), as well as on the low-intensity bike rides, where I can pedal at a much higher RPM and resistance than before, while my heart rate remains in the proper zone.

I've also noticed strength improvements each week, and in general my fitness is much better and my daily energy level is much higher.

Some downsides:
- In order to really build strength, I feel like I need a third day each week. Not enough time.
- One high intensity cardio day per week also feels lacking. But there's nowhere that another one would fit, unless I pile two workouts per day.
- Long cardio day basically takes an entire afternoon, and the repetitive nature of it is conducive to injury.
- This is a pretty intense workout schedule. Definitely worried about burnout, but I'm trying to listen to my body. If I notice that I'm regressing, I'll add in more rest.

Anyway, there it is. If anyone has suggestions to improve this workout plan, please let me know!

Comments

Popular posts from this blog

Why Korean Is Hard For Native English Speakers

A couple of days ago, as an experiment, I wrote my first blog post ever in a non-English language . It was an attempt to explain some of the reasons that Korean is hard to learn for native English speakers, so I figured I might as well try to write it in Korean. Those of you who actually read Korean can see how awkward the attempt was =). In any case, the post came from an email conversation I had with The Korean from  Ask a Korean , a fantastically well-written blog about all things Korea from the perspective of a Korean who moved to the United States during high school. Since I tend to geek out on language things, I figured I might as well post part of that conversation. An edited version follows. --------- Out of the languages that I've attempted to learn so far, Korean has been the hardest. I've done a lot of meta thinking about learning Korean, and I think there are a number of reasons it's difficult for non-Koreans (and especially Westerners) to learn: 1) Obvi...

10 other things South Korea does better than anywhere else

Recently this article about 10 things that South Korea does better than anywhere else  has been making the rounds on social media, but when I first read it, I couldn't tell if it was sincere or satire. A few of the items on the list are not very positive, such as "overworking" and "using credit cards". So, I thought I would try to put together a better list. Here are 10 other things South Korea does better than anywhere else: 1) Small side dishes, a.k.a. " banchan " (반찬) Banchan are by far my favorite aspect of Korean cuisine. Rather than the "appetizer and main dish" approach of the West, a Korean meal is essentially built around small dishes. Even a 5,000 won (about $5 USD) meal at a mall food court will come with two to four banchan in addition to the "main", and often people will actually choose restaurants based  on the banchan (e.g., seolleongtang , or beef bone broth soup, places tend to have the tastiest kimchi). Ther...

Pushing Python Performance With Parallelization

TL;DR: For certain types of programs, you can take advantage of idiosyncrasies in the Python interpreter and the host operating system to create real shared memory between processes and get some pretty good parallelization. Premature optimization is the root of all evil. As a developer, you've probably heard this before, and what it means basically is that you shouldn't waste time optimizing code unless it's already doing what you want it to do. We also live in an era of seemingly unlimited resources with AWS/Google Compute, and often the easiest way to get higher throughput in your programs or service is just to pay for more instances. But sometimes it's fun to see what sort of performance we can get on a simple laptop (and save some cash at the same time). So anyway ... I've been working on this thing, and it took too damn long to run, and I needed to run it lots and lots of times ... so, it was time to optimize. Basic optimization has two main steps: 1) P...