Thus endith my first blog con¬≠test. And a very cool ride it was.

My good friends at Click¬≠free, a Cana¬≠dian backup tech¬≠no¬≠logy com¬≠pany, agreed to provide the prizes (Click¬≠free Trans¬≠former SE) for a blog con¬≠test chal¬≠len¬≠ging folks to provide there best (or worst I guess) backup hor¬≠ror story.

I‚Äôve received some rather good entries. Check out the com¬≠ments in the ori¬≠gin¬≠al post for the entire list, but here‚Äôs a couple of excerpts to give you the idea:

In a multi-developer game devel­op­ment envir­on­ment:

We updated our loc¬≠al SVN repos and tried to work with the new changes that we were all mak¬≠ing (plus unknow¬≠ingly the changes this oth¬≠er guy made)‚Ķ only the game ended up crash¬≠ing. It worked fine before this latest update and no one was sup¬≠posed to have made any changes that would cause this prob¬≠lem, and yet, here it was, the game was crash¬≠ing. Franticly we looked at all the changes ‚Äúwe‚ÄĚ had made for the prob¬≠lem (remem¬≠ber we did not know this guy had checked any¬≠thing in) and argue¬≠ments rose over who was at fault of this issue (oddly no one fingered the par¬≠tic¬≠u¬≠lar pro¬≠gram¬≠mer in ques¬≠tion since we didn‚Äôt know he had com¬≠mit¬≠ted any¬≠thing, plus it was 4am and no one was think¬≠ing straight).

Stolen Grad-stu¬≠dent Thes¬≠is data:

I got a frantic call from a grad stu¬≠dent once, say¬≠ing that someone had broken in and stolen his com¬≠puter with all his thes¬≠is data and his 3‚ĀĄ4 fin¬≠ished draft thes¬≠is ‚ÄĒ two years of data col¬≠lec¬≠tion research and writ¬≠ing gone!

Win­ners?

In the next week or so I‚Äôll be review¬≠ing the entries and noti¬≠fy¬≠ing the win¬≠ners. And yes, there will be a blog post about it. Stay tuned!