As you may know, I came to Germany this week for CeBIT, and my wife and I are sightseeing in Berlin over the weekend. This trip very closely mirrors my first visit to Germany, in 2003. And it’s amazing how much has changed from a communications perspective.
My first trip to Germany was in May 2003: I was speaking at a local event called Windows-Forum 2003. The topic, amusingly, was Longhorn Server. Which of course would not ship until 2008. But we didn’t know that at the time.
Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!
"*" indicates required fields
At that time, cell phones were a thing, but smartphones were not, so PDAs were still a thing. Wi-Fi had just come to laptops in a big way in Windows XP. And Windows XP Service Pack 2 (SP2), which would fix the rampant security holes that that access had originally brought with it (among other issues), was still a year away.
Because our last trip to Europe by that time was 10 years earlier, when we had visited my father in London, we decided to make a week of it. My wife flew out with two of our friends, and we planned to take in sights along the Rhine, and in Munich and Rothenberg. (We would begin our annual home swaps two years later, in 2005. So this return to Europe was a big deal for us, and it would inspire future international travel.)
Also at that time, our son had just turned five, and our daughter was two. So they were not coming along, and would instead stay with their grandparents.
And this presented the first challenge. Facing the normal separation anxiety, and with none of the now-familiar communication capabilities available to us, we decided to rent an international cellphone. This way, we could call our kids from time to time and check-in. And if something bad happened back home, their grandparents could reach us too.
Back in those days, that meant finding a local place that rented us a Nokia candy bar phone. And going to pick it up in person. In East Boston. Which in 2003 was nearly inaccessible because of the “Big Dig” construction that was then changing I93 from a raised highway into a tunnel below what is now green space in the middle of Boston.
Anyway, we printed out the directions to the place using MapQuest (again, 2003) and headed into Boston. And got lost, because all the roads were different from what the service described because of the construction. There were no such thing as timely updates back then, let alone real-time updates. But we eventually found it.
The trip itself was incredible. In fact, one of our most memorable hotel stays to this day happened then, when we stayed in a castle above the Rhine river: We sat behind the parapet, or battlement at the top of the castle watching low, flat boats, trains, and cars move slowly on and next to the river in the dark, drinking wine. Absolutely amazing.
We visited St. Goar, Bacharach, and other places along the river, experienced incredible German Rieslings for the first time, and then made our way towards Munich, and after that, Rothenberg and finally back to Cologne.
But the most memorable thing about that trip, really, was the rental phone.
As you might know, my son is deaf. He can hear thanks to technology: He now has two cochlear implants, one on each side, and he does amazingly well. (He only had one implant in 2003.) Aside from the fact he is wearing what appears to be hearing aids, you’d never know, as he speaks clearly and appears to hear very well. (It’s a bit more complicated than that, but that’s beside the point.)
To me in 2003, the ability to call my son, from a cellphone, while speeding down the Autobahn on the way to Munich, in this case, was … amazing. (Yes, someone else was driving.) So much so that I literally started crying when I handed the phone back to my wife. On the call, he could hear me, he could understand me, and we could converse normally. It was magic.
Most of my other connectivity attempts on that trip were less successful: Wi-Fi access in hotels and other places was either slow or non-existent back then, and I was mostly offline for the week. But I will never forget that phone call. It changed everything for me, and opened up the possibility that this stuff would only keep getting better and better.
Which of course it has. So this week, when I flew out to Germany ahead of my wife, my son was driving his car out to upstate New York to return to school after Spring Break. We communicate by text and phone, like anyone else, and he called home to his mom along the way, using the hands-free tech in the car, to let her know everything was OK.
Meanwhile, I’ve been in constant communication with my wife by phone, text, and email during this trip: Doing so is so inexpensive that I’ll just call it free. And now that she’s here—she landed recently and is heading to the hotel as I write this—that easy communication continues.
What a world, right?
<p>We had "smartphones" back in 2003, it's just that they weren't called that back then. I know because I carried a Samsung SPH i700 Windows Mobile phone throughout my days in Law School. To be honest, I had no problems with it and I believe that it was the only kind of "smartphone" of it's kind in the market. The phone came with a stylus, but you could also effect the screen by simply touching it. </p><p><br></p><p>That phone is now proudly displayed in my Tech Museum, along with my Motorola StarTac Black (VIP) edition, Palm Treo (windows Mobile), and all my other tech.</p><p><br></p><p>It's funny on where we are today with mobile tech. Back in 2003, my use for the Samsung SPH i700 was primarily email, web, games, camera, and minor document management. Today, it's like the same thing, but better, much better in terms of ease of use and the expansive ecosystem of application software. It's just so strikingly weird how Microsoft failed to envision on how to improve and evolve that platform. If they had, there wouldn't be (first) an iPhone and (later) Android. LOL…just so weird.</p><p><br></p><p>I, too, also used Mapquest as my primary source for map and direction, despite my efforts to give MSFT's Streets and Maps the designation as my preferred solution.</p>