Slashdot Mirror

← Back to Stories (view on slashdot.org)

The Exact Cause of the Zune Meltdown

Posted by kdawson on from the off-by-one-every-four dept.

An anonymous reader writes "The Zune 30 failure became national news when it happened just three days ago. The source code for the bad driver leaked soon after, and now, someone has come up with a very detailed explanation for where the code was bad as well as a number of solutions to deal with it. From a coding/QA standpoint, one has to wonder how this bug was missed if the quality assurance team wasn't slacking off. Worse yet: this bug affects every Windows CE device carrying this driver."

4 of 465 comments (clear)

  1. Why is this a surprise? by deanston · · Score: 0, Troll

    And who uses Windows CE?

  2. Re:Warning, Y2.1K bug. by LostCluster · · Score: 0, Troll

    Okay, tell the programming instructors that there's no need to teach Hello World examples, because there's already code that does that.

  3. Talked-about layoffs at MSFT by postmortem · · Score: 0, Troll

    This is what happens when there are no serious consequences for the bad work.

    They seriously need to lay off the bottom 10% (or 20?) of their workforce for the first time in company lifetime. Some people ought to be scared of bad work they do. There's no way for any company that all 100% of workforce are productive and useful.
    I bet remaining workforce and end-users would thank them.

  4. Let's make sure this gets installed everywhere ... by trolltalk.com · · Score: 0, Troll

    " Worse yet: this bug affects every Windows CE device carrying this driver. "

    So who volunteers to "fix" this driver so that it implements this "feature" every day, and also "works" on all Windows platforms?

    Better yet, anyone want to bet that Microsoft will do something like this (purposefully break Windows) in an update, to force people to adopt Windows7?

    --
    Kevin Smith on Prince