Richard Huff's Seattle Social Blog

After almost two years since the release of the Forerunner 305, Garmin has finally announced the release of an upgrade in their line of personal fitness computers. A comparison of the two models makes me think that the main difference between the 305 and new 405 is the form factor. The 405 does sport a new, wireless sync capability (using an included USB ANT™ stick), but I never felt that the older USB cradle represented an inconvenience. In fact, the combination of sync and charge in the older USB cradle was really great for traveling. The 405 will require carrying the "stick" and a separate charger. Is that an upgrade?

In all honesty, it is unfair to make an assessment by comparing manufacturer specs -- especially if the products are from the same manufacturer. For whatever reason most manufacturers have an uncanny inability to convey their products' key value propositions. Take, for example, almost any PC laptop maker (e.g., Dell, HP, and Sony). Can you tell the difference between a Dell Vostro™, Latitude™ or Precision™? It's like a exercise in graph theory every time you want to make a purchasing decision. But I digress.

The Garmin Forerunner 405 could be a quantum leap in the Forerunner evolution, as the 305 was to the 205. I won't know until I actually own one and can make a "real world" judgement. The catch is that I'm not compelled to upgrade, yet. Somebody else needs to be the first penguin in the water this time. Unless, that is, Garmin wants to send me an evaluation unit.

You've all heard the stories about thousand dollar phone bills when traveling internationally with an iPhone. As someone that once sent a very costly e-mail (~$1,900) via my Cingular 3G wireless Internet service while roaming in the Pisa, Italy airport, I can attest to a valid concern about mindlessly roaming with an iPhone. Although I already had the discounted international roaming package ($5.99/month) for my voice service, it does not cover any of the data service that is so important to the iPhone. Enter AT&T's "Data Global Plans for iPhone". At just $24.99/month, you can head off most of the scary data roaming costs associated with using the iPhone internationally. Thirty-six countries are covered in the plan, and you can start and stop the service at any time (i.e., there's no new contract associated with the feature).

Both times I've run the Capital City Half Marathon (2005, 2007) it has rained. The nice thing about the rain (in both cases) was that it only rained hard enough to provide a bit of cooling.

Melissa kicked me out of bed at 5:00 AM, and we drove from Seattle to Olympia. Parking and getting to the start was no problem. I'm also happy to report that this year's shirt was gray, long-sleeve, technical, and printed with an appealing logo design. Very nice! Worth keeping. I can toss another cotton race shirt.

There was only a moment to stay warm inside a Starbucks before our group was called to the start line. A cannon -- not a pistol or air horn -- signaled that the race was on. The quintessential Western Washington scenery of Puget Sound vistas and Douglas Fir trees lined the race course. The dome of the State Capital Building would appear and disappear in the trees as we made our way around the city. Melissa pulled ahead, and finished a full 15 minutes before me. She was grinning ear-to-ear when I saw her near the finish (where Chuck took the above photo of me) because she knew that they were handing out finisher metals -- something they didn't do in 2005, and something I'm still sore about.

We rewarded ourselves with a breakfast at McMenamin's Spar Cafe.

With the 2007 Seattle to Portland Classic (STP) just around the corner (July 14th and 15th), we're taking every chance we can get to "be in the saddle". Being back from a business trip earlier than expected allowed me to join Melissa and a couple other friends for the 2007 Skagit Spring Classic on May 12th. The Skagit Classic is in its 17th year, and offers four different routes: 25 mile, 45 mile, 62 mile, and 100 mile. Most of us rode the 62-mile route (a "metric century"), which included a picturesque climb up Chuckanut Drive. My fears of excessive automobile traffic competing for the extremely narrow roadway were somewhat unfounded.

The ride started out pretty rough. Although the terrain was flat for the first several miles, we had to battle head-on, gale force winds, heavy dust and poor quality pavement. The relative protection of the trees and elevation once we reached Chuckanut Drive gave us a much needed reprieve. Most of the route (until we dropped back into the Skagit Valley flatlands, near the end) was good. Volunteers with the sponsor (Skagit Bicycle Club) staffed rest stops along the route, and handed out homemade cookies and other snack foods.

My only regret is that I didn't take my camera.

When you're way too old for Hasbro's Tonka Toys, you can rent the adult version and have more fun than you ever did as a child.  That's exactly what we did this weekend in McCall, Idaho.  The little "bobcat" provided two full days of excitment as we did some much needed work around Sadie's new garage.  Now all I need is a couple acres of bare land and a bobcat of my own.

Between 1998 and early 2000, analog dialup started to slowly slip as ADSL and cable services were deployed. There was no doubt that faster, full-time connections were needed for both homes and businesses. After all, these were the heady days of the dotcom bubble. Telecom companies and cable providers were just not deploying services quickly enough. It's no conspiracy theory that telecom companies didn't want to provide the service because it threatened to undermine an existing business, and that cable companies had quite a bit of network upgrading to perform before wide deployment could even occur. Furthermore, both ADSL and cable were -- for the most part -- the purview of the incumbent telecom and cable companies. Internet Service Providers, try as they may [1][2], didn't have a chance in these markets.

The dotcom crash, 9/11/01, and the telecom scandals didn't help things. What did occur following those disruptions was the popularization of Wi-Fi (IEEE 802.11). Also, the value of the Internet barely skipped a beat. E-commerce, digital music, voice-over-IP and video were almost entirely grass-roots movements, driving the necessity for bandwidth ever higher. Podcasting, video blogging, and television distribution through Apple's iTunes are happening today -- not at some distant future time. The ADSL and cable bottlenecks are the dilemma that continue to constrict progress.

Without touching on the distinction between theoretical and real bandwidth, let's continue the relative network speeds graph from Part I of this post.

Although both ADSL and cable services have begun to deliver faster speeds, they're both dwarfed by the network performances most of us experience every day in our home and office environments. Furthermore, they are not technically different from the ADSL and cable services provided in 1998 -- they're just much closer to their maximum potential. To put my point into greater relief, the following graph presents a comparison between the connection speeds of my actual networks as I write the post.

The server where my blog exists is in a data center next to Seattle's Space Needle. It connects to the physical Internet via a full-duplex, 100 megabit per second Ethernet port. My office has both an 802.11g Wi-Fi access point (half-duplex, 54 megabits per second) and a full-duplex, 100 megabit per second Ethernet network. The fastest Internet connection I could have installed at my office -- without paying several thousand dollars per month -- was 7 megabit per second (down) by 1 megabit per second (up) ADSL. Most people don't even have that fast of a connection.

With the growing popularity of gigabit per second Ethernet and the new 802.11n Wi-Fi specification, the disparity will only grow.

In summary, new Internet applications such as podcasting, music and video distribution are continuing to necessitate higher network speeds. Whereas local area networks based on Ethernet, fiber and Wi-Fi regularly operate at speeds between 100 and 1,000 megabits per second, telecom and cable companies have reached the end of their bandwidth potential using the existing copper and coax infrastructure. A move to ADSL2+ or Hybrid-Fiber-Coax will not be enough to address this ever-increasing disparity. Part III of this post will explore possible futures.