Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I found a PDF that confirms the story I heard, and also has information I wasn't aware of until today:

https://availabilitydigest.com/public_articles/0411/sidekick...

Details are on page 3.

* The Sidekick servers were moved to Microsoft, and I believe they were moved from where I last saw them, which was at T-Mobile's data center in Washington.

* There weren't a heck of a lot of Solaris experts at Microsoft at that time.

* According to the PDF above, someone had posted a job ad for a database administrator for the project, two months before the database blew up.

So if we connect the dots (this is speculation Microsoft, don't sue me):

It seems possible that the database for the Sidekick service was the responsibility of someone at T-Mobile or Danger, until Microsoft acquired Danger. My hunch is that it was probably TMo, because the founder of Danger left to go start Android in 2003. By the time Microsoft bought Danger in 2008, a lot of the original Danger folks were working on Android.

It sure seems like the outage was most likely caused by an inexperienced DBA taking responsibility for a database that had been the responsibility of the same DBA (at Danger, or more likely, TMo) for over half a decade.

And that ONE database outage probably changed the entire course of mobile phone history. IMHO, Microsoft wouldn't have purchased Nokia in 2014 if Danger hadn't blown up in 2008. And Danger was way ahead of the iPhone and Android in 2005.

In some alternate universe, there is no Android, there is just Microsoft Sidekick and Apple iPhone.



I always thought it was hilarious that a company called Danger lost everybody's data. The connection to Microsoft only makes it better.


> I always thought it was hilarious that a company called Danger lost everybody's data. The connection to Microsoft only makes it better.

Cursed marketing.

Besides the fact that we didn't have any real money to promote phones at T-Mobile (and I think we were the only US carrier with the hiptop) -

Would you believe that the first hiptop came out the same week as 9/11?!

So it was this phone that was arguably two-ish years ahead of the iPhone, but nobody seemed to know it existed, until it got some traction via sheer word of mouth. Everyone who used the HipTop basically wouldn't go back to anything else at all. The HipTop had that 'addictive' quality that the iPhone had. It was nothing like the Blackberry, where people largely used it for a single killer app.


It was announced in Sep 2001, came out in Oct 2002 (these long waits were then common for mobile phones).

I first read a review of it in a Mar 2003 magazine.


Good point. During that era, a lot of the legacy devices like the famous Nokia brick, the dev work on those was done with actual physical devices.

The smartphone stuff, a lot of that development was running in emulators, which likely reduced the time-to-market.

I distinctly remember seeing devs working on future phones in emulators, but most of the devices we sold were just upgrades to existing devices.

That was probably the moment when Nokia and Ericsson and RIM should have been paying attention to what was happening just south of Microsoft in Bellevue. But none of those three companies had a significant presence in the area at the time, AFAIK. The Silicon Valley folks were flying in every single day. I'd argue that this is what killed Sprint too; they were five hours from anyone. The predecessor of AT&T Wireless was so close to T-Mobile, you could drive from one HQ to the other in under fifteen minutes and you could stop off at Microsoft on the way over.

Definitely an example of the synergies that are possible when you have a couple of tech titans who are less than 90 minutes away from each other via Southwest Airlines.


Cites my employers, the Register, albeit with a typo and no link.

« Oracle and Sun fingered for Sidekick fiasco

https://www.theregister.com/2009/10/19/sidekick_rac/

Just think what they'll do to Microsoft when they merge »




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: