Who... What are you?
I was running earlier tonight and around mile 7 I was going up a steep, winding, dark hill. Near the top a couple was walking their dog. They saw the flashing lights on my shoes and wrists and, when I got close to them, the woman said, "We were trying to figure out what you were."

"I'm a runner."

[/running] [permanent link]

1264352606
1:37:50. New half marathon PR.

--
==================================================================
This mobile text message is brought to you by AT&T

[/mobile] [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]

Looking back...
As I look back at code I wrote a decade ago as an undergrad, I often find lots of little things that can be done better. For instance, in one file I found that reversing the order in which two functions were called would have eliminated a half dozen conditionals from one of the functions and would have resulted in the same expected behavior, but with fewer lines of code and a lower cyclomatic complexity.

[/code] [permanent link]