Then my wife wonders why I spend so much time on the computer.
The challenge, however, is to know what all those numbers you're collecting really mean in the grand scheme of things. Does knowing your average heart rate for bike rides over 20 miles provide you any insight into how you're going to perform on race day? Or, does your average run pace on the Wednesday evening run foretell your half-marathon time? It may, & it may not. Sometimes when race day arrives you have to put the unimportant data off to the side & look more closely at the important stuff: How far do I have to go? How much harder can I go? Have I gone too hard already?
There's a place for all this good stuff, as long as you know the physiological feedback which equates to the number: What does an eight-minute mile on the run, or a 1:30 for 100 yards in the swim, or a 20-mile-per-hour speed when you're in big ring/small cog feel like? 'Cause, what do you do on the race day when your battery dies, or the numbers aren't matching up with the ones for which you were hoping?
Why should being a tri-geek or a runner, or a swimmer be like work? There are times my father has marveled at the stuff I do (writing & all that good stuff), because the best stuff gets done during the moments I manage to shoehorn (or crowbar) out of the middle of my work day. Yes, I do get "stuff" done there...probably because I don't spend as much time keeping track of it.
