Skip to main content

Back to Barefoot (Running)!

So I finally got over to a nice rubberized track today to do some sprints with my new stopwatch. It was a sad, sad state of affairs. My legs felt tired and "mushy" before I even started, but I figured (or hoped) that it would go away once I warmed up. No such luck. I suppose running MWF this week really did me in. It was so bad that I almost tripped three times in the middle of my 100m time trial, and the time was embarrassing enough that middle school girls would probably beat me. I think the tripping may have been caused by my shoes, though. I switched back to my running shoes for the sprints, and it's the first time I've worn them running in about 6 weeks. Usually I wear thin-soled Adidas shoes that are most certainly not meant for running, with the hope that the thin heel will help promote mid-foot striking rather than heel-striking. But when I go back to my running shoes now, it feels like I'm wearing huge pillows on my feet.

Short aside: I had to give up on the barefoot treadmill running after a month or so, as it was too painful for my feet. My soles kept blistering, and one of my arches started hurting too, so I switched back to shoes.

Despite the demoralizing sprints, it was still a great workout. I spoke to a former Stanford Track member a couple weeks ago, and he confirmed that the team indeed did some barefoot training, mainly in the form of strides on the grassy infield. So after my sprints, I decided to do a couple 100-130m strides on the grass. It felt incredible! I can't remember the last time I ran with any significant velocity barefoot. It's amazing feeling the grass beneath your feet, feeling the entire spring action that your foot naturally has, just feeling everything. I'm totally sold. But I would still recommend to anyone considering giving barefoot running a try to take it slow at first. Your feet probably are not used to it, and they need to build up strength in order to avoid injury.

Till next time, keep it real, and real means no shoes!

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