Technically Speaking

A little over half a year into this blog I realize it has become something different from what I originally intended.  Frankly, that's mostly due to a thing called "time".  It takes more time than I anticipated writing posts.  It takes a LOT more time reading others blogs.  This time has to fit around family, work, training, and other interests.  The other big factor has been that as a family we do a lot.  Seriously, have you seen the quarterly retrospectives (1stQ & 2ndQ)?  That means that there's always a race recap to write and rarely time for other thoughts.

So, what's missing?  Those that know me well know that I research the heck out of any interest I have.  I'm an engineer at heart and I dig into the details.  Don't get me wrong - I know in the worlds of cycling and multisport that I'm a newbie.  However, I also know that my knack for research gives me a knowledge base that exceeds a lot of rookies (and some more experienced folk as well).  This is "book smarts" and not "street smarts" obviously and I have no intention of misleading anyone.  However, I think a lot of what I learn by just being me can be beneficial to a lot of people.  Sharing my research and analysis was one of the things I originally intended to do with this blog.  In some cases, I hope these types of posts can be helpful for the masses.  In some I may invite the blogosphere to disprove me and set me straight.  Either way, knowledge is to be gained and as G.I. Joe used to say ....... "Knowing is half the battle."


So, what should you expect?  Expect to see a post of this nature at least every other week if not weekly.  Sometimes it will be gear related, sometimes it will be training theory, sometimes ...... well, it could be anything.  Early topics will be things like troubleshooting a Garmin speed/cadence sensor, pH levels in sport drinks, a workaround for accessing Garmin files without the usual "plug-ins", etc.  Only two questions I need help answering:

1) What topics would you like me to delve into?

2) What should I call this feature?

Thanks for reading!