Skip to main content

Make a Resolution to Workout Harder

If you want a simple tip to make your 2010 workouts more effective than those of 2009, here it is in two words: workout harder.

I'm always amazed at the average intensity I see when I go to the gym. A typical observed weightlifting workout involves 8-10 reps at too low a weight, followed by 4-5 minutes of sitting around (waiting for your heart rate to drop from 100 to 80?), repeat, move on to another exercise, etc. Yes, it's better to be in the gym doing something than nothing, but these workouts aren't really doing much for you.

When I started working out seriously back in July or so, I made circuit workouts a regular part of my routine. I choose two exercises that work different muscle groups (for example, pull-ups and lunges), and do supersets (do one set of one exercise, then move immediately to the next) with one minute rests in between. I work out hard enough that my heart is really pumping by the end of each superset. The one minute rest is just enough to bring my heart rate down to a reasonable level before going again. Then I rest for a couple minutes while choosing my next superset.

I've found this type of workout to be much more effective for me than what I did before. Sure, I get what-are-you-crazy stares from people, but I'm sore after almost every workout, and I've gained considerable strength and endurance since starting. Also, this type of circuit training works aerobic capacity as well as strength. But the best thing is that you can literally do a 30 minute workout (including warmup) that works your whole body and leaves you exhausted.

Works for me. Give it a shot!

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...