It's JavaScript's fault that I ran slow

What I've been staring at 

Today's run (street): 3.2 miles

I have a consulting practice that focuses on digital media business and technology. I'm in the process of expanding my portfolio of services. That involves including more strategic partners and re-branding my website. I'm spending time on the development site whenever I can fit it in. Although I get input from my partners, I'm handling both the web design and the technology. This is fun for me, but staring at HTML and JavaScript code for hours really wears me out.

I'm hoping that will explain the gap between my perceived effort (PE) on today's run and my actual performance. I didn't expect to see impressive numbers when I checked my Garmin after my run, but I ended up running over a minute slower than how the run felt. It was a more challenging workout than I'd anticipated. It was also a sign that I haven't gained back as much speed as I hoped I would by now.

It was interesting to see that the Garmin data showed that my average cadence was up measurably, compared to my last few runs (174 vs. 168 SPM). So my turnover was good. Had I opened up my stride a little more, my pace time would have likely reflected my PE. It's something to think about on my next run. But I won't be thinking about it until Saturday, because Hal gives me a rest day tomorrow. Great, more time to code my site.

Where JavaScript and running meet

JSON born

Today's run (street): 2.5 miles

In my past life I studied programming languages and applied it at various jobs throughout my career. I liked the combination of structure and art that comes from programming. The structure was the syntax and logic and the art was the creation of an experience that came from typing many++ lines of code.

This blog allows me to do some fun stuff with HTML, but lately I've been playing with JavaScript. I've challenged myself to writing a process that will pull JSON data from Daily Mile that I can parse, query, calculate and display on the site. Daily Mile has widgets that do that, but they display more info than I want to show. With the work I've done so far, I can see that this will be a real challenge.

I was thinking about my approach to writing this process as I ran through my neighborhood this morning. It was a nice distraction and, more than once, I found myself further along on my route than I'd realized. I thought I was running faster than what the numbers showed, but perhaps thinking deeply and fast pacing are not compatible concepts. I ended up with a respectable time along with some new ideas about approaching my new coding project.