obstacles

today was back to the grind of work work work. a new project is in the works and it means that i need to learn some basic .net via visual studio pro, arcgis server and geodatabase setup via sql server. yikes. i'm designing the interface of the web application which means being able to work with the code (not necessarily write it - thank goodness). i enjoy the challenge of learning new things, but the big man wants prototypes of this done in a few weeks. atleast the programmer that i'm working with is patient, communicative and cool.

in other news, i was at the gym tonight and had an interesting conversation.

guy: "i saw you on your bike the other day"
me: "oh yea, where? you shoulda said hi"
guy: "well i didn't want to startle you with the horn... but you were doing this" (he holds out his hand and signals like you would to turn) "do you remember that?"
me: "well, i do that a lot - every time i turn in fact"
guy: "oh"

this was of course no surprise as i am most often on my bike. however i guess turn signals are not generally understood by the non-cycling public.

breaking news... it has been discovered that 25% of the general population believes that 75% of the cycling population suffer from random, involuntary hand and arm movements.

it's hard not to laugh when people say things like that to you because the natural response is that they are joking.

only they're not.

and speaking of chickens... in more random news, jess and i are concocting a plan to setup an obstacle course in my backyard. is this possible? it needs to have small logs and perhaps a log pile... and i need to be able to easily assemble and disassemble at will as they mow the lawn here once a week. i'm thinking something along the line of tent stakes and randomly collected logs, however decreasing the possibility of impaling myself in my own backyard would be nice.