PyWeek - I just deleted all my files

Here is a sad story. I just deleted all my files for the project.

Getting ready for the submission I typed: 

  $ find . .*pyc -delete

Instead of: 

  $ find . -name *.pyc -delete

That's the first time I've done such. And it was all f'ing complete. Menus. Levels. High Scores. Not to mention bundles of little bug fixes around score accumulation and polishing. And reiserfsck only recovered the friggin' README ... I was sweating bullets trying to shut down all the daemon processes probably writing to /home before I could unmount it and start the failed recovery.

Anyhow, I at least had a tarball of a very incomplete version from 2 days ago. So that's my submission. No menus, no levels, no high scores. And lots of bugs.

— djfroofy_c_ on 2008/09/13 22:09 of Solo Foo
— edited on 2008/09/13 23:32

Comments: (log in to comment)

By bencoder on 2008/09/13 22:24:

ah man that sucks :( i'm sorry

By pymike on 2008/09/13 23:00:

Ouch, that sucks bad. Yet another story about why you should use version control

By djfroofy_c_ on 2008/09/13 23:04:

@pymike

Errrr. Wrong. I was using version control - mercurial. The .hg directory was deleted as well.

By joey101 on 2008/09/13 23:15:

Perhaps you should have synced your repo on the net. such as on freehg.org or bitbucket.

I guess this is another advantage of working on a team apposed to solo. Sorry that it all go deleted :( And your game looked really neat also!

By nilsf on 2008/09/13 23:23:

:(

By djfroofy_c_ on 2008/09/13 23:31:

@joey101

Thanks for the positive remarks on the game. You can actually play the incomplete version I had a backup of - which I've submitted.

I also use bitbucket for other projects, but was just hacking it out for this week - I wasn't really taking it too seriously. I have to remind myself of this in light of this "tragedy." Haha, it was fun - just disappointing not having a completed game. Too bad reiserfs sucks for recovery.

By richard on 2008/09/13 23:48:

Damn, you lost all your work *and* you were using a source repository? That's some terrible source repository design there. Sorry you lost all your hard work!

By phren on 2008/09/13 23:51:

Ouch! A real shame and I can only imagine how much it disappoints you. :(

By sjbrown on 2008/09/14 00:13:

sucks. my gut was in a knot reading that.

By djfroofy_c_ on 2008/09/14 00:25:

@richard

Terrible source repository design? I don't think this is any different than bazaar or git which both store the repository data in the clone's root directory (.hg, .bzr, or .git). My clone happened to only exist on my machine.

By richard on 2008/09/14 00:28:

@djfroofy_c_ compared to, say, SVN or CVS it's terrible :)

By richard on 2008/09/14 00:29:

Anyhoo, this isn't a time for a repository brand flamewar. I feel your pain regardless :(

By djfroofy_c_ on 2008/09/14 00:40:

@richard

Sure. A VCS flameware would get realllllly boring. Thanks for feeling my pain, and thanks for hosting this comp.

By riq on 2008/09/14 00:40:

ouch! :-(

By Tee on 2008/09/14 00:44:

I'd also like to say, ouch. Just the thought of that makes me shiver. Sorry to hear about it. :(

By Juanj Conti on 2008/09/14 01:06:

Sorry

By RB[0] on 2008/09/14 01:43:

Dang man - that really sucks :(

By Archwyrm on 2008/09/14 02:13:

Wow, I am quite sorry to read this. Judging from the circumstances, you are probably one of those people who "knows better", which I am sure makes the whole thing that much more irritating. =/

By myke on 2008/09/27 22:02:

source control rules i followed for this compo (and after reading your entry, will ALWAYS be doing for my projects):

  • commit early, commit often. as soon as a new feature works, or any kind of progress is made, push a commit. who cares if there's hundreds of commits for a week-long project. efficiently storing many tiny commits is the source control system's problem, not mine.
  • keep the master repository on a dedicated server machine in such a way that the repository is NEVER directly edited. preferably don't even use the server for dev work. in my case i was using a computer at home and work to dev on, and a separate headless server for the repository, so at any given time there existed 3 copies of my game with only a few hours difference at most between them.
  • when making a release, do a final commit, then do a checkout to a brand new directory. prune all files not needed for release from this folder, not the one used to develop the game.

sorry to hear you lost the final version of your game, based on what you did submit it was probably really good.

By HanClinto on 2008/09/28 01:17:

myke: For your step #3, SVN includes an "export" command so that you don't have to prune any of the hidden .svn folders.