After waiting six months on a pre-order waiting list, I finally got my Fitbit two months ago. I was really looking forward to it — as a big fan of the Nike+ running tracking system, I was excited about Fitbit’s promise to not only track my running and walking, but to track my sleep patterns as well. And the design was extremely seductive — small in size, elegantly combining form and function (it doesn’t have a clip, it is a clip), and with a magical blue led screen that is invisible when the device is off. How could I resist?

And I was right: I love the Fitbit!

But I don’t want to use it any more. How is that possible?

First, though, you may be asking “What is Fitbit?” Fitbit is a personal health tracking system consisting of a small electronic device that you clip to your body to track your movements and a web site that uses the data from those movements to give you detailed reports and analysis of your fitness and health. The Fitbit device contains an accelerometer to detect anything from a single running stride to tossing and turning in your sleep, and it wirelessly syncs to your computer via a small radio transmitter. The Fitbit has a small digital display indicating the number of steps you’ve taken, how far you’ve walked or run, and how many calories you’ve burned.

Basically, you clip the Fitbit on your waist all day long, and to a wristband at night, to collect 24/7 data about your body’s movements. The Fitbit web site then slices and dices that data to present some pretty fascinating insights into your personal health.

Sounds simple? It’s supposed to. There is an emerging trend in personal electronics and software to stop bothering users with long explanations of “how it works”, and to instead keep the interactions simple and just make sure the damn things work.  Fitbit is right on that wave. The documentation doesn’t say much about how it works, the web site doesn’t have a big “how it works” page. You’re just supposed to start using it.

So Fitbit cuts to the chase in most of their user experience designs. In fact, I can’t find anything on the Fitbit home page that says “Fitbit is …”. Fitbit is what it does, which is count your movements and interpret that information.

I think that’s part of Fitbit’s strategy: to experiment with giving users a minimal level of explanation to get people focused on changing their behavior and thus their health, and not on requiring users to constantly be manipulating the technology.

Getting Fitbit

Let’s first discuss the centerpiece of the Fitbit system, the Fitbit device itself. It’s about the size of a money clip or a small pack of gum, clips easily to clothing and fits easily in a pocket. Some users complain that it is easy to lose, and while I managed to hold on to it for two months, I can only attribute that to luck. I am really impressed by the “clip” form factor (versus a wristband, a strap, a card, a keyfob). Given the required size, it’s a clever solution.

The digital display is incredibly nice to look at. When it’s off, it’s just a detail-less smooth black surface. When you press the Fitbit’s single button, however, the display shines through the now-translucent plastic like shining a flashlight through your fingertip.

When you bring the device near the charging/base station, it automatically uploads the latest data from the device. The base station is clever, but I think it over-fetishizes the Fitbit itself by literally placing it on a pedestal, as many upright docking stations do for the iPhone. And its 18″ cord is overkill. While it is quite clever to allow the device to sync automatically, you still have to turn your computer on in the first place, and if you’ve got a laptop you have to plug in the base station anyway. So syncing isn’t invisible for most people, I suspect, but is rather a conscientious and deliberate daily act.

A syncing solution like the original iPod Shuffle’s, where the device itself had a USB plug built-in, would permit charging and syncing without an additional base station device and, as I contend, without adding an additional sync action for most users. A Bluetooth version to sync with high-end laptops without charging would be even better.

The web site is fantastic. The data displays are lovely, and it’s easy to get around and play with your data. I do have problems with many of the specific information design and charting decisions, but I am not going to complain because the Fitbit folks are constantly evolving and improving the site, tweaking features, responding to user feedback, adding new stuff.

Interestingly, you can use the Fitbit web dashboard without owning a Fitbit. First of all, the site lets you manually enter your food consumption information in order to establish your caloric intake each day. Also, it lets you manually enter your exercise activities as well.

I actually suspect the designers must have conscientiously kept the site device-agnostic, to support future Fitbit devices and to invite non-Fitbit users to join the web community.

Using the device as a pedometer, which is by far Fitbit’s core function, is simple. I can see the distance I’ve walked at any time during the day, and when I get home I can see a day-by-day report on the web of how far I’ve walked, and how far I walk each day on average. The device’s step-counting accuracy is astonishingly accurate: I did a test, walking and counting up to 1000 steps in my head, then checked the Fitbit and saw it counted 1004. That’s plenty accurate for me.

For running, Fitbit detects the nuances of difference between a running and walking motion, and then recalculates your distance traveled (based on longer stride length) and calories burned accordingly. There is simply need to tell Fitbit that you’re running and not walking. It’s smart enough to tell, based only on the nature of the data it’s collecting. As for running accuracy, I wasn’t able to do a counting test, but the distances Fitbit reported on several over-5-mile runs were 10-20% different from the distances reported in Google Maps. Far from ideal, but on par with the similar inaccuracy of Nike+.

Where Fitbit gets really clever, however, is with sleeping. Obviously a motion sensor isn’t able to tell if you are sleeping or just lying on your ass watching TV. Fitbit requires you to press and hold the devices’s single button for a few seconds, putting the device into a kind of “special activity” mode. Fitbit comes with a surprisingly non-obtrusive wristband that holds the Fitbit device while you sleep. As you sleep, the Fitbit detects your body’s movements and uses these cues to determine how long it took you to actually fall asleep, how many times, and precisely when, you moved around in the middle of the night, and when you woke up. In the morning, you press and hold the button again to indicate that you’re awake and walking around again.

The sleep data collected is fascinating, and this alone is worth the price of admission. You probably have no idea about how long it takes you to fall asleep, or how often you toss and turn. I certainly didn’t, and was delighted to see the results. I found it incredibly interesting to see the day-by-day durations of my sleeps for an entire month (little more 2 hours more than a few times, around 6 hours most of the time, and 12 hours on one blessed Friday night).

For other activities, such as cycling or weightlifting, Fitbit isn’t so smart. For such things, Fitbit literally requires you to manually manipulate the data. Again, for people in highly-structured weight loss programs where counting calories in and out is important, Fitbit’s web dashboard offers the ability to manually enter your non-walking or running activities to make sure your overall caloric burn rate is kept accurate.

An amusingly large number of people in the forums ask about the fitbit’s ability to measure calories burnt during sex, some with a measure of sexual bravado (”wear on my hip?”), others innocently but rather seriously dedicated to counting every calorie burned. While I admire the free spirited nature of these inquirers, I cannot offer any additional insight into this matter as I, perhaps overly romantically, still beleive that some things remain well beyond quantification.

The Fitbit Ecosystem

The Fitbit web site is constantly changing, and they keep adding features to the site, extending the functionality of the fixed hardware system. This is part of the clever concept that the features entirely lie in the interpretation of data. It’s a radical simplification of what software is all about: Fitbit’s one motion sensor and one binary button (ternary if you count the long 2-second press, and potentially more if you add longer presses, or even double and triple presses as on the iPhone earbud controller) have the potential to enable a lot more interaction and communication than one might think at first blush.

In a way, they are squeezing as much functionality out of the tech as possible. Fitbit is a small embodyment of Don Norman’s recent claim that technology leads and design follows. For Fitbit, it’s an inspired design response to the question “how many things can we do with just this one bit of technology”?

To contrast this with Nike+ for a moment, Fitbit feels far more like a living thing, run by engaged people dedicated to incremental changes in response to the actual usage by their community and feedback in their incredibly active and helpful forums. It’s a Web 2.0 product. Nike+, however, is a more traditional product, with huge and infrequent X.0 product launches. Nike+ stagnated with the same beautiful and innovative — but buggy and slow — web site for years, only to upgrade this year to a new, buggier, and unfortunately even more awkward user interface. Nike+ still never remembers users passwords, for example. I wish Nike+ would follow Flitbit’s lead when it comes to incremental, simple improvements. Focus on a UI that can scale and evolve, and not on one that is sexy and “bold”.

Product Conclusions

There are probably two kinds of Fitbit customers. First, casual users: people who want to know more about what they do with their bodies, people who are curious about their health and the potential to use technology to keep closer tabs on how well they’re doing. This describes my interest in Fitbit.

The second group is serious users: people who are actively trying to change their personal health behaviors and want a way to measure those changes. If you’re trying to change an overly-sedentary lifestyle, to lose weight through careful monitoring of calories burned versus consumed, Fitbit might be a huge help. For people involved in a structured weight loss program, a device that adds to that regime is perfectly normal. But I walk plenty each day (4-5 miles every day). I am an athlete and run often, but I don’t count calories. I’m not trying to lose weight. I use Nike+ to measure my special activities (running), but I don’t want a new device attached to me all the time just to give me data about my normal activities, just to satisfy my curiosity.

So while I found Fitbit useful and delightful, it was only temporarily. But that’s okay. It’s a fantastic tool for self-analysis, to get to know your sleep patterns, your typical daily walking distance. Great information. But once you have that information, if you’re not engaged in a program to change those things, you’re done with Fitbit. I know everything Fitbit can tell me. Maybe I’ll try it again in six months or a year, to see if I’ve changed. I’m a casual user.

The Fitbit is not what I and other casual users might have hoped it would be. It’s not going to be a permanent part of your life, a constant and consistent way to monitor your health. The biggest obstacle to this, I think, is unfortunately still technological. It’s just too big to carry with you in every possible context, so you end up taking it on and off over and over again all day. When you change clothes, you have to move it from one garment to another. At night, you have to strap on a wristband and clip it to that. You have to take it off in the shower.

Inevitably, I ended up forgetting to bring it to work occasionally. Or I’d have it unclipped for part of a day. Which is far worse than it sounds: If you miss a day of walking in a week, it completely ruins the accuracy of your weekly average. Miss a few days in a month, and your monthly average is shot to hell. Fitbit lets you manually enter your information, but I’ll be damned if I’m going to do Fitbit’s job for it! You’ve got have your Fitbit on your person almost 90% of the time for it to produce accurate trends and summary results, the kind of results that justify integrating it into your life in such a serious and committed way.

If the Fitbit was the size of a fingernail, attached with waterproof glue or embedded under my skin, well, then we’re talking. But because of its size, it becomes one more thing to inhabit my intimate attention space, something I have to remember to never leave home without, like my phone, my wallet, and my pants. It’s like having a little adopted pet you have to take care of all day.

In short, you just can’t lead a normal life with Fitbit. If there’s one thing I’ve learned from the Fitbit experience, a lesson about the future of personal informatics, it’s that we simply won’t have accurate and reliable personal systems until the devices themselves are immune to these everyday emergencies and accidents and inconveniences. Until they’re virtually invisible and forgettable, probably embedded under the skin, we will be forced to consider personal informatic hardware as intrusive medical devices rather than as the ethereal, ambient data sources I think many people envision.

If you want an informatically-based weight loss program, with increased walking as a core element, and if you want to count calories in and out, Fitbit is for you and might help you with your program over the months and years.

If you are interested in just finding out about your body and how you use it, it’s great for that, too. Give it a spin, then hand it off to another person. Want mine?

• Leave a Note (5)

Where’s Chris been? Why, I’ve been working, swimming, biking, and running.

The latter three were all brought together two weeks ago in the Philadelphia Triathlon (my second triathlon ever — my first was the New York Triathlon which I finished last summer), for which I have been cramming in a lot of training in recent months (to the obvious expense of blogging). On July 28th, it all paid off. It’s like working for a year on a major web site and finally launching it, only better.

I grew up in Philadelphia, but I don’t think I remember it ever being as beautiful as it was during my race. It had been raining all week, but by the time Sunday rolled around the sky was clear and sunny.

The swim was in the Schuylkill River, which for my entire childhood was synonymous with pollution and filth. But to my great delight the river was clear and clean, an absolute joy to swim in. It was, in fact, my first open-water swim in fresh water since I began serious swim training. The 1-mile swim began at the St. Joseph’s Boathouse (my father’s alma mater) and passed under a bridge, finally finishing on the other side of the river.

The bike and run were all though Fairmount Park, including two loops on the bike passing right in front of the Philadelphia Museum of Art (known in Philly as “The Art Museum”). It was hard not to have the Rocky Theme in my head every time I passed by those step. I’ll confess that I actually downloaded the song a few weeks before in a fit of Philadelphia nostalgia.

Most of the bike course was through shady woods or country roads or grassy hills. The run was along the bank of the river. You’d hardly know you were in a city park. Again, I don’t remember Fairmount Park being so tranquil and lovely in the 1970s.

The Philly Triathlon is about half the size of the New York version (2000 vs. 5000 people), which makes it sooo much more intimate and manageable. After doing both, I am reluctant to want to ever do New York again when I can always do Philly instead. I am, of course, now trying to find one even smaller to do, maybe even before this season is through.

In the New York Triathlon last year I didn’t do as well as I’d hoped, but this time around I managed to reduce my overall time by almost 20%. My final, official time: Swim (1 mile): 30:02; Bike (25 mile): 1:17; Run (10k): 58:06. Total, with transitions: 2:53:26! I worked my way through the swim, kicked ass on the bike, but I petered out a little on the run, I guess, running what I think is my slowest 10k ever.

In the end I came in 844th of 1306 men. Next time I know I’ll crack the top 50%!

Maybe I’m not as verbose as I was last year, but there’s more to see in my Flickr photo set, and my Mom even put up a video on YouTube!

• Leave a Note (1)

At 11:01am Sunday morning, in 90-degree heat, I crossed the finish line in Central Park and completed my year-long goal of finishing the New York City Triathlon. I was exhausted and frustrated (more on that later), but at that moment, as soon as I stopped running and realized I was done, I was overcome with a profound visceral joy.

I’ve been actively training for the triathlon for a little less than a year, but it’s been an idle dream of mine for several years. Since way back in my teenage years I’ve been an sometime runner and cyclist. But last August I did a run/bike duathlon that was more than a little thrilling, and then, in September, I began training as a swimmer, a step that for all intents and purposes was the first step on the road to my first triathlon.

For those of you unfamiliar with triathlon (it is conventional to leave out the definite article), it is a race of various lengths consisting of swim, bike, and run stages, in that order. Between each stage, competitors are required to “transition” from the mindset and the equipment from one sport to those of the next sport as fast as they can. Triathlon lengths range from “sprint” distances (approx .5mi/12mi/3mi) to the classic “Ironman” length (2.4mi, 112mi ,26mi). The New York Triathlon is “Olympic distance”: approximately 1-mile swim, 25-mile bike, and 6-mile run.

For me this is a sort of fulfillment of a family tradition: My father is a runner and a high-school cross-country team captain, my brother and several aunts and uncles are long distance runners and certified marathoners, my stepfather is a cyclist who biked from coast to coast, my mother swims and bikes, her father (my grandfather) is a living family legend of long-distance running (completing many marathons at an age when most men play shuffleboard), and his wife, my grandmother, has been a competitive diver, swimmer, racewalker… and, yes, a triathlete. My effort was at some level dedicated to and inspired by them all, especially my grandmother. Thank you, family!

Ready!

The preparation for any triathlon, especially in the days leading up to the event itself, is elaborate to say the least. I’ve included a photo here of all the stuff I needed to pack for the race, from bike helmet and gloves, three different pairs of shoes, goggles and extra goggles, extra contact lenses, body lubricant (yep), water bottles with water and energy drinks of various sorts, and countless other little things — and this doesn’t even include the full-body wetsuit!

(In the lower left corner you will see the Field Notes notebook I dedicated exclusively to planning for the race.)

The triathlon is really a weekend-long event, with a check-in and briefing about the race on Friday, dropping off the bike and taking a tour of the transition area on Saturday, and waking up at 2:30am on Sunday to eat breakfast before heading over to the race site. During the week leading up to the event, it was increasingly hard to think about anything else. Every meal was carefully planned, every bedtime strictly enforced. The development of a sore throat Friday morning worried me far more than it normally would have. I don’t think I’ve ever been so conscious of how my body was working.

Set!

My car service got me to the start area at 4:30. The 3 hours between the time I laid out my gear in front of my bike to the time my age group (men 34-39) jumped in the water went by as if it were only a few minutes. During these twilight hours I was Twittering and uploading photographs to help distract me from the nervousness under the surface (you can check out my live Tweetlog here).

Next thing I knew I was in my wetsuit and walking down the gangplank with a hundred other men in their late 30s, listening to a megaphone telling us that we would start in 30 seconds.

Go!

I got in the water, heard the siren blare, and started swimming.

Before this, I had reconned the conditions in the water. The waves didn’t seem bad. The current seemed strong, but I knew it was slowing down. I didn’t see any garbage in the river along our race course, but I did see some nasty looking jellyfish along the shoreline. My summers in Cape Cod have innoculated me against the fear of most varieties of small icky marine wildlife, so I was pretty confident about what would be my first open water long distance swim.

Even the initial mayhem of the swim, with arms and legs kicking about like crazy (I was even kicked in the face and almost lost my goggles), I felt like things were under control.

But after only a hundred meters, things changed dramatically for me. I was suddenly and precipitously exhausted. I couldn’t hold up the pace I was accustomed to — I’d swam a mile or more in the pool dozens of times before and never tired like this. I was so winded I had to stop swimming and simply drift on my back for a few moments. In fact, this cycle characterized my whole swim — crawl stroke for a few minutes, followed by a few minutes of aimless drifting. The current that the earlier starting athletes enjoyed had by this time come to a standstill, so when I drifted it wasn’t even necessarily in the right direction.

In short, things were going pretty badly from the outset.

I didn’t figure it out it at the time, but later on, after the race, I realized that the sore throat I’d been wishing away had, moving southwards, matured into an acute bronchitis, constricting my breath as if someone were sitting on my chest. The rest of the triathlon would be shaped by this biological fact, but for me in the heat of competition I could only think to myself “What the hell is wrong with me? Try harder! Breathe harder!” It’s funny how quickly and easily we can blame our problems on our characters instead of our bodies.

Somehow, I finished the swim and staggered ashore. I learned later that others were not so fortunate: one man actually died during the swim. It’s unclear how it happened, but I am glad I played it safe and floated gently on my back (with wetsuit buoyancy assistance) whenever I thought anything didn’t feel right.

I knew I was falling well short of my target pace, but I didn’t know by how much. I later learned I completed the swim in almost double the time I targeted, but during the race I simply knew the bike stage was my chance to catch up. Still, I felt faint and winded as I climbed into the saddle.

Biking up the Henry Hudson Parkway, however, was a joy. I had fallen so far behind that, as a relatively strong cyclist, I was able to pass a great many people during the 25 miles, and managed to keep a pace very close to my objective, despite my shortness of breath. And cycling on a closed highway, with only a small number of riders around you, is a thrill that’s hard to describe.

In the final run, I again found myself in the same condition as I felt in the river: each burst of even low-level exertion would be quickly followed by gasps for air. As with the swim, I again found myself coasting — walking — for a great deal of the running stage.

Finishing!

Along the way, there were thousands of spectators and officials cheering the triathletes on. Most of the time I loved the “great jobs” and “doing greats”, but when I was drifting down the river on my back to catch my breath, or gasping for air and walking through Central Park, it was a little frustrating to be urged to a level of achievement I felt I just didn’t have in me. In the big picture, however, the sting of even these bittersweet encouragements kept me focused on the primary objective: to finish the whole thing, to try my hardest, and to never give up.

Similarly, the pre-race best-wishes from friends in the real world and via the Internet drove me on. The best part was seeing my family and a few friends staked out along the way. Some were following my performance via a SMS text-messaging service announcing my times as I completed each stage — pretty cool. But the best part was seeing my family with a home-made sign with my name on it.

When I finally crossed the finish line, I was surrounded by congratulations from the race staff. I was given a nifty medal, had my photo taken (all along the course, photographers from Brightroom.com took photos of athletes, many of which I’ve included on my Flickr set for the triathlon), and was given an endless supply of branded sports drinks.

Repeat!

Knowing that my performance Sunday was impaired by my health, I am totally psyched to do this again, and soon, to see what I can really do. I’m not waiting until next year. I’m looking for the next triathlon now. I’m hooked.

• Leave a Note (12)

I am currently training for my first triathlon, the New York Triathlon on July 20.

(Holy crap, that’s only 9 weeks away!)

Anyway, last weekend I competed in the Prospect Park Mother’s Day Duathlon right here in Brooklyn. This was my second duathlon (I ran my first one last August), and this time I did a lot better: I came in 23rd out of over 120 competitors. I came in 6th place in my 24-39 age group, too. If you’re my parents or if you are thinking about racing against me someday, you can see the complete results here.

A photographer, Len Lopate, was on site taking pictures during the race (the top pic is his). Check out his site to see his other shots, including me at the start and on the bike.

Most happily (and most surprisingly) at the end of the race I discovered that the race organizers had free WiFi set up around the finish area, and as people finished the race the staff was updating their web site with the results in real time. Those of us with web-enabled devices were able to check our own times and everyone else’s as we waited for the rest of the athletes to finish the race. Pretty cool.

I’m pretty nervous about July’s triathlon, but these duathlons have helped me a lot. They help me actually get some idea about what switching from biking to running in rapid succession really feels like, and in a competitive environment, too. I’ve been able to meet other multisport athletes, too, although it would be more accurate to say I got a chance to scope them out but not really meet them. I still feel like an outsider in a fairly exclusive club.

Other lessons learned:

• Transitions: I need to figure out how to get my bike gear on more quickly. I could have come in the top 20 if I hadn’t been so leisurely about my first transition.
• Nutrition: The duathlon is probably half as long as the triathlon in sheer time, which means I need twice as much stored up energy. I’m going to need to pay closer attention to my diet on race day. I began to feel a little weak towards the end of the race, but moments after finishing I was shocked to find myself getting dizzy and then vomiting in the bushes. Must remember to avoid acidy fruit drinks for breakfast!
• Pacing: I’m going to have to figure out my final pace. I intended to take the bike part pretty easy, but I think I pushed myself pretty hard in the end and lost some energy for the final run.

I’m not sure if I will have a chance to compete again between now and July 20 — maybe I can find a 10k to join or something — but I really enjoy this and look forward to more.

• Leave a Note (3)

This is the least humiliating frame from my whole clip.

I’ve recently started a swimming training program so I can competently complete my weakest part of the trifecta: Running, biking, and swimming. Hopefully by next summer I will be ready for my goal, to compete in the New York City Triathlon.

An interesting aspect of this swim class is the use of technology. In our very first meeting, the coach shot underwater videos of each student crossing the pool, capturing all of our flailing arms and gasping breaths. He then wrote up a critique of each student’s swimming technique and gave a CD with all of the videos and critiques to each of us, giving us all a powerful insight into what we are doing right and wrong in the water. It’s astonishing how many things I can instantly see that I need to improve, especially when I watch my own video next to that of, say, Olympian Ian Thorpe.

What’s great about this is how incredibly low-fi and accessible the whole deal was. You would think that underwater cameras as a training tool would be reserved only for competitive swimmers at the top of their game. But there I am! The video camera looked like a regular consumer model attached to a long pole with some kind of jerry-rigged periscope involved, and immersed in the water. The coach shot by simply walking along the edge of the pool and following each of us as we swam across. And because it’s digital, it was easy for him to bring 20 copies of the videos on CD-ROM to the next class a week later.

He’ll be recording us a few more times over the 12-week course, so we can track our improvement. I can’t tell you how much I look forward to the next taping. I swear, I dream about swimming now.

This blog post has been brought to you by “Our Swimmer”, by Wire:

• Leave a Note (2)

This weekend I built my first single-speed bicycle. It’s not a fixed-gear or track bike — it has a single gear in the back with a freewheel mechanism, and as you can see it has brakes, too.

For years I’ve wanted a single-speed bike just to see what all the fuss is about, but also I wanted to experiment with what I’ve heard are the benefits of single-speed training. But most importantly I also wanted a basic bike that I would feel comfortable leaving locked up in my lobby or even on the street for hours or days on end. My other two bikes are a just little too attractive to thieves, so I can never leave them anywhere for long. Basically I needed a kick-around set of wheels.

Speaking of thieves, this whole project has a little bit of a shadow over it: Over the years I’ve been collecting enough of my own bike parts for this project, but I was missing just one critical piece: the frame. It finally occurred to me that a pile of abandoned bikes locked up in my building’s lobby might be ripe for the picking. There was one bike, an old Nishiki, that looked my size and had the requisite horizontal dropouts. I knew the bike hadn’t been touched in two years, but still I put up several signs in the building’s lobby seeking the bike’s owner. After a few weeks of hearing nothing, I made my move and, yes, I stole the bike.

I like to think I salvaged it, and I did my deed during a high-traffic part of the day so as many fellow residents as possible would see me doing my work (I merely unbolted the rear wheel, which was the only part locked up). But honestly I am still a little afraid that the bike’s owner will someday return from his three-year ’round-the-world hike, or kick his drug addiction, or whatever has kept him from his wheels, and he will see me on a bike whose dents and angles look a lot like those of his beloved Nishiki. Such worries are the wages of my sin, I guess.

I stripped the bike of nearly every part it had, dramatically reducing the weight by replacing the bike’s original parts with my own slightly-higher-quality parts (the original handlebars were made of steel!) or by just leaving certain parts off the rebuild entirely. The only part I’m (literally) stuck with is the seatpost: it seems the previous owner installed a replacement post that was too big for the frame, so he simply hammered the thing into the seat tube as far as it would go. As a result, the seat is immovably positioned about an inch too low for me. Even if I figure out how to remove the seatpost, I’m not sure a properly-sized seatpost would even work anymore since the seat tube seems permanently expanded.

On my first test ride of about 15 miles, I came to enjoy the single-speed’s simplicity, and it was surprising how often I managed to keep up a steady pace without shifting gears. On the hills I had to stand up and hammer, but even then I managed to keep a good pace.

The best part was that with this beater bike I can stop riding, lock up the bike in the park, and then do a few miles running on foot. The toe clips require me to wear normal sneakers, so I didn’t need to pack an extra pair of shoes. And, as I said, I’m not overly worried about the bike being stolen. Hooray!

• Leave a Note (6)

I’m the skinhead in the red shirt.

A year ago I entered my first bike race. It didn’t go well.

Yesterday I entered my second race, and my first multi-sport race. It was a “duathlon” — running and bicycling — around Brooklyn’s lovely Prospect Park in the twilight hours of a perfect summer weekday.

How did I get myself into this situation? It all started so innocently, in a late-night AIM chat with Adam Greenfield in which I mentioned that I heard about an event called the “Brooklyn BricK Duathlon“, and that it looked like something I might be able to handle. Next thing I knew, Adam and I were both registering online at the same time, spontaneously and impulsively. There’s no way either of us would have done this if it wasn’t for the support and encouragement you get from having even just one person to commit with you.

The start was at 7:00pm on a Wednesday night, just as the park was getting dark and the streetlights were coming on. This alone made the race attractive to me: I am not a morning person, and my evenings on Fridays and Saturdays tend to involve fine wines and good spirits into the wee hours. This makes early morning weekend racing a bit of a problem for me. Having a whole day to eat properly and prepare mentally for the race really helped.

The BricK was what they call “sprint distance”, a cynical term for what is still an endurance event for most mortals. It consisted of:

• A 3/4 mile run through wooded trails.
• A 10 mile bike around the park loop.
• A 3.2 mile run through the woods and around the meadow.

So how did I do? I think I did pretty well. Of 133 entrants, and 89 finishers, I came in 35th overall (results here). I did equally well in both the run and bike phases, and felt pretty good at the end, too. Which means I am definitely doing this again.

The event was inspiring, to say the least. Adam and I felt like we were surrounded by superhuman professional athletes, and the carbon-fiber stealth-fighter looking machines most of them had put ours to shame: me on an 18-year-old steel frame, Adam on a single-speed (!). Many of the competitors were tricked out in team gear, ripped with muscles, sleekened hairless, and sharing war stories about the other triathlons they’d triumphed in lately. Nonetheless, the whole event was really low key, very DiY and ad hoc, and completely devoid of the kind of aggression I felt all around me in when I was racing in a cycling pack. In a triathlon/duathlon, drafting behind other cyclists is illegal, which means it’s just you and the wind — which is how I like to roll.

The race was brisk, of course, but the vibe was pure fun. A great first-time experience. The best part was on the last run, where the race leaders would pass the rest of us on their return trip to the finish line. Most of the top five finishers took the time to cheer on the rest of us as they ran by us: “great job, way to go, great pace!”. That meant the world to me.

I want to commend the information design by the kids who chalked the directional arrows on the roads. The running route was fairly complex, the maps they prepared were god-awful messes, and the race director could barely describe it without just confusing people even further. But some young kids were sent on a mission to put directional arrows on the paths using chalk, and they did a great job. The route doubled-back on itself, and there were two runs on the same trail, so the signage needed to indicate which way to turn on the way out and which way to turn on the way back. Here’s what they came up with. Not bad, huh?

• Leave a Note (3)

“Simple is Best” is the motto of Jinbei Yamada, founder of Japanese bicycle maker Arrow Bicycles. I love this motto for its elegant phrasing, completely devoid of pretention and utterly consistent with its own meaning. There is no false dichotomy of “form versus function” to drive a pointless wedge between functional and decorative simplicity and pure visual design elegance. Who needs ten complicated laws when one law sums it up so well?

Arrow makes less than 1,000 bikes per year, and most of them are custom-ordered to some degree. As for the bikes themselves, I’ve not had the pleasure of seeing or riding one, but they look lovely. There are no logos to be seen, either, which is something I deeply appreciate.

• Leave a Note (6)