Staten Island Half Marathon
Sunday was the Staten Island Half Marathon. I've been dealing with overuse injuries as of late, my IT-band has been acting up and I strained my right hamstring.

I wasn't sure if I'd be running or not, and the temperature was predicted to be in the low- to mid-50's, so I wore my coldgear; I didn't want to end up with hypothermia again if I was standing around for 2 hours in shorts.

It turned out that one of my teammates, Liz, wasn't sure if she'd be able to finish. We decided to run together. And we did. We finished with the exact same time of 2:34:00. I kept her from stopping and she kept me from going to fast and re-injuring myself.

It took me an hour longer to finish the race than it normally would, but I think it went quite well. My hamstring actually felt better after the run. My IT-band was a little sore the next day, but it was better by Tuesday.

Running at the slower pace, I was able to actually look around and enjoy the scenery. The shores Staten Island were not as bad as I was expecting. Over all, it was a good recovery run. A 13.1 mile recovery run.

[/running] [permanent link]

Bing!
It has come to my attention that searching bing for pictures of closed doors yields pictures of my DeLorean.

[/dmc] [permanent link]

Self Documenting Code
Despite what you think about your code, it is not self documenting. When writing code add comments, describe what a function does, explain why you're using that convoluted pointer arithmetic and bit shifting. I'm sure it makes sense now, but someday you'll have to go back and look at it and figure out what the hell you were doing. Or worse, I'll have to go back and look at it and figure out what the hell you were doing.

Sometimes it is important to have some sort of separate documentation for the code; maybe some UML or ER diagrams, maybe some English text. Use what ever it takes to explain what you were doing. Do not paste snippets of your code into the text and call it documentation.That is not documentation, that is code.

[/code] [permanent link]

A Weekend at the Races
Tomorrow is the Fifth Avenue Mile and Sunday is the Marathon Tune-Up. I'm looking forward to both. If all goes well, I should be done with tomorrow's race in under six minutes. Sunday's race I'm aiming for a time between 135 and 140 minutes. We'll see what happens...

[/running] [permanent link]

Don't Call it a Comeback
On June fourth, I was running in the Tourne on a trail I first ran twenty years ago, a trail I've run hundreds if not thousands of times before. On that morning, my foot came down on a wet rock at just the wrong angle, slipped just enough and I rolled my ankle. Not only did I roll the joint, I came down on it with enough force to break it; a fact I would learn when I final saw a doctor about it on June ninth.

No surgery was required, but I was unable to run for three months. I was finally cleared to run. The plan was to start with short distances, about a quarter mile, on a rubberized track then build up from there, moving on to treadmills and eventually roads and trails. I was instructed to spend six months rebuilding my 60 mile per week base.

On the morning of September 11 (a day I will never forget and a morning that will always make me feel a bit uneasy), I took to the track for the first time. I started by walking a mile. As I finished the fourth lap, I said a prayer, asking God to give me the run I needed and the wisdom to know when to stop. I queued up my playlist: AC\DC's "Back in Black" and LL Cool J's "Mama Said Knock You Out." I took my first stride.

I've been progressing well in the last two weeks; pushing it on some days, resting when necessary. Though the short, slow distances have been frustrating, it feel good to be running again. Every stride I take I'm reminded of everything I love about the sport.

It's good to be back.

[/running] [permanent link]

Writing

"You need strong emotion, whether it's fiery or depressed, an extreme state of mind. I think in any art form it's the case." -- Daniel Ash

Maybe it's my lack of experience. Maybe it's my lack of talent. I tried to sit down and write music for the song known as Ravage in the new naming scheme, but I failed miserably. When I try to force it, like I did tonight, nothing comes out right. I have ideas, I can hear them in my head, but without that inspiration, without that emotion, nothing I produce sounds right.

I've been too happy recently and it's destroyed my creativity. I get the urge, I have the inspiration, to write when I feel negative emotions. I need anger; I need depression. It is in dealing with these emotions that I am able to write.

I have tried several times to force myself to feel this way. This usually buys me a few minutes in which I can write, but it often fails. Because the emotions are artificial, the results are mediocre at best.

I find this situation to be quite frustrating. I want to move forward with this album, but without that inspiration I am unable to do anything.

In the meantime, I'm slowly teaching myself to play guitar and, to a much lesser extent, a keyboard-style synthesizer. I've also been going through materials my music teacher friend gave me to learn some basic music theory. Hopefully once I find that needed inspiration, or find a way to work without being angry or depressed, this new knowledge will make things easier.

[/album] [permanent link]

Revision Control
One could argue that this should be filed under the Unix category, but this post is more about the album than it is about the Concurrent Versions System.

Friday night I created a CVS repository on this server to manage album related files. After discussing it with rskutins, we agreed on several key points.

First, with changes being made a little more frequently than before, it would be best to have some way to track what was going on, and to be able to roll back to a previous version if the changes don't quite work out. Second, we wanted to have a way to organize several files for each song, for instance, lyrics, notes, bass tabs, drum tabs, etc. Last, and maybe the most important reason for the reorganization, we wanted to move away from the numbering scheme that was in place. Each song was numbered from 0 to 17. This was fine until we realized 11 was likely to be the first track on the album.

Now the album is stored in a CVS repository. This will keep a version history of each file, allow us to simultaneously work on parts of the album, and merge our changes.

Within this repository we now have a tree structure where each song has its own directory. The directory will hold any and all files related to that song. In an effort to move away from the numbering scheme, an arbitrary naming convention was mutually agreed upon. The songs are now known by names such as Soundwave, Ravage, Frenzy, and Rumble.

The album is starting to come together. I feel motivated to work on it and recently I've found myself inspired to write. Now if only I had time.

Omlette listened to the Accidental Mix I posted (of the song now known as Soundwave) and gave me some feedback.

It sounded ominous. I don't know how else to describe it since I'm not familiar w/ either artist. Oh wait. Were you mixing your own stuff?

Ominous seems like it could be a good thing given the current direction of the album.

If anyone else takes the time to listen to it, I'd appreciate any comments or suggestions. If you don't have it, my contact information is on this page.

[/album] [permanent link]

Another Demo Update
Two weeks! Ha! It's been closer to two months.

A few days ago I had some time so I sat down with the ProTools set up again. After considering some advice from jlight, I decided to record a second track of the bass line. I decided to use my Yamaha for the second track, as I had used my Fender for the original recording back in June. The two instruments have different characteristics in their sounds and the two playing together seems to add a "fullness" to the sound.

So all I had to do was record 24 seconds of bass and put together a mix. This should take, what, 15 minutes? It took 45 just to record. Once again ProTools repeatedly crashed. When it wasn't crashing, it would report an error and stop recording. Does anyone know if there are updates for ProTools LE 7.1 that will fix this issue? As it stands now, I can't run ProTools for more than a few seconds without disabling multi-core support on my CPU. I have multiple processors. It is a multi-threaded application. It should run better... But I'll save this for that upcoming ProTools rant I keep promising.

Anyway, after about an hour and fifteen minutes, I got two mixes complete. One of them was accidental and sounds, "interesting." The other is closer to what I had in mind. While I wait for feedback on the actual mix from certain people, everyone is free to enjoy the accidental mix found here.

If anyone actually listens to it, I'd be happy to accept any comments and criticism.

[/album] [permanent link]

Demo -- Update
Rskutins recorded his drum part and sent it to me via the wonders of TCP/IP netowrking. On Friday night I finally had enough time (and motivation) to start recording.

I spent a lot of time fighting with ProTools. It repeatedly crashed. Often, when it didn't crash, it simply stopped recording and reported that an error had occurred. I'm remembering this for the ProTools rant that will be coming in the future.

After 45 minutes I had recorded about 6 seconds of vocals and the 24 second bass line. The next block of Copious Free Time(TM) I have, I'll begin the rough mix of the three parts. Hopefully ProTools won't crash as often during that phase.

With any luck, it'll be mixed in the next week or two.

[/album] [permanent link]

Demo
In the next few weeks we are going to attempt to record and roughly mix a demo of a short track which will serve as an introduction to the album.

Currently known as 11, it is a very short piece in 4/4 time at 80bpm. It is in the key of B minor and the spoken words are taken from a quote attributed to Nietzsche.

What upsets me is not that you lied to me, but that from now on I can no longer believe you.

This short demo will hopefully get me motivated enough to put more time into the album.

More information will be posted when it becomes available.

[/album] [permanent link]

A Brief History
Last Summer, my friend, rskutins, and I decided we were going to write an album. He got out his drum machine, being smaller and easier to store and carry than a full kit, and I got out my bass and we started putting together some pieces that were... not good.

We had little direction, I was afraid to play things outside of my comfort zone, and we had some problems communicating. This project quickly fell apart, but we never completely gave up the idea.

In March I found the inspiration I needed. I talked to rskutins and we started working on an album again. This time, fueled by strong emotion, both fiery and depressed, I started by writing lyrics.

Not all are complete, but there are about 15 sets of lyrics for us to use as a starting point. Rskutins has tweaked the lyrics in some places to make them fit a better rhythm while still maintaining the intent of the words. I am quite pleased by what he has done.

Based on these lyrics we have begun writing short pieces here and there when we feel inspired. Rskutins has laid down some pretty good beats to start with. I've been attempting to learn some basic music theory and trying to apply those ideas to the layers on top of what rskutins has written already.

And that's where we are now. Still learning, still writing. Our day jobs have slowed down our progress considerably so it could very well take until the Autumn before we're ready to record and mix the album.

[/album] [permanent link]

Product Review: ASICS Cumulus-11
This is the third installment of my running product reviews. Last time I said I'd discuss my "current running shoe" but my again I'm a liar. I'm still going to discuss the ASICS Cumulus-11, but it is no longer my current running shoe.

I purchased the Cumulus-11 based on my love of the Cumulus-10, without really trying them. This turned out to be a mistake. The Cumulus-11 is a fine update to the Cumulus-10; however, the changes are better for some runners than others.

The heel of the Cumulus-11 is noticeably firmer than that of the 10. Because of this change, I no longer get adequate compression and cushioning from these shoes. These shoes are not as firm as the Tailwinds previously reviewed either and are closer to the Cumulus-10 than to the Tailwinds. I never had the feeling of running in clogs with the Cumulus-11, but they were firm enough that old injuries were aggravated.

The Cumulus-11 is still on store shelves (at least it was at Fleet Feet this past weekend) and should also be available on-line through retailers such as EastBay. I recommend this shoe to a runner who liked the feel of the Cumulus-10 but had issues with it being too soft.

Next time, we'll discuss my current running shoe, the Nike Vomero+ 4. No really, I have three pairs of these to burn through, I'll be using them for a while.

[/running/reviews] [permanent link]

Product Review: ASICS Cumulus-10
This is the second installment of my running product reviews. Last time I said I'd discuss my "current running shoe" but my training has turned me into a liar. I'm still going to discuss the ASICS Cumulus-10, but it is no longer my current running shoe.

At this point, the Cumulus-10 can still be found, although supplies are limited. I recently tried to purchase a second pair of these and was unable to find them in my size. I could have had a 9.5 or a 12, but not the 10.5 I needed.

When the Nike Tailwinds no longer provided adequate cushioning, I had to find a new shoe, one that would work for a lighter runner. After reading reviews online and in magazines, particularly Runner's World, I went over to Fleet Feet in Montclair and talked to the sales staff there.

After trying on a few pairs, I decided on the Cumulus-10 but wanted to wait until after the Brooklyn Half Marathon, a week away, before breaking in new shoes. This is not what happened. Because of the lack of cushioning in the Tailwinds, I ended up with horrible shin splints during my lunch time run the day before Brooklyn. I called up fleet feet, asked them to hold a pair of the Cumulus-10s for me and I picked them up that evening. I ran in them for the first time the next morning in the Brooklyn Half.

Those shoes were amazing. They were soft enough to provide the compression needed for good cushioning at my weight. And while they were soft, they weren't mushy either. The ASICS GEL cushioning system is in place in both the heel and the forefoot, providing ample shock absorption for heel strikes and mid- to fore-foot strikes.

The toe box was slightly narrow, but starting the laces one hole up from the bottom provided enough extra space while keeping my foot firmly in place.

The sole in the forefoot is wide; wider than the sole in the Tailwinds. This provides support for the foot during the toe-off portion of the stride.

The Cumulus-10 served me well until I had put just under 600 miles on them. At that point the cushioning was worn down and not as effective as it once was. I retired them about a week after the NYC Half Marathon in August giving me about 12 weeks worth of running. In actuality, I should have retired them after about 10 weeks.

I recommend the ASICS Cumulus-10 for lighter runners with normal to low arches. Left over stock of the Cumulus-10 can be found at EastBay's website for $69.99 (both men's and women's), although many sizes are unavailable at this time.

Next time, we'll discuss my current running shoe, the ASICS Cumulus-11. I've been slacking a bit so I only have about 250 miles on this pair so far. Hopefully I'll post the review before I hit 500 miles and retire these.

[/running/reviews] [permanent link]

Product Review: Nike Tailwind 2008
Welcome to a new feature on this blog. I'm going spend some time writing what I think of various running related items such as shoes, clothes, and energy gels.

My first review is the Nike Tailwind 2008 running shoe. At this point, they're a little hard to find as they have been replaced by the Tailwind 2009. From what I've read about the 2009 edition, not much has changed so much of this should still be relevant.

What first drew me to this running shoe was the Air Max cushioning. Like many Nikes, the heel contained the Air pockets. Unlike many other Nikes, these also had the Air Max cushioning in the forefoot.

I tried them on and they were snug, but not too tight. Perfect. They were already on sale by time I was buying them. Even better.

I ran about 400 miles in my first pair in about six months time, and replaced them with another pair which lasted about another four months. During this time the shoes served me well on treadmills as well as road and trail courses.

These shoes, however, are best for heavier runners. The cushioning is very firm and needs extra weight to compress properly for maximum impact absorption. When I first started wearing the Tailwinds, I was about two months into my training and was about 210lbs. As I ran more, I lost more weight. At 180lbs the shoes were still quite good. At 160lbs they still provided adequate cushioning, although I started to feel my runs more.

The Tailwinds served me well until I was under 140lbs. Below that and they feel like running in clogs.

I recommend the Nike Tailwinds for heavier runners with normal to low arches. The men's Tailwind 2009 can be found on the EastBay website for $79.99 (99.99 for women's) as of this writing, making them a relatively affordable running shoe.

Next time, we'll discuss my current running shoe, the ASICS Cumulus-10.

[/running/reviews] [permanent link]