- ...bunch of stuff...
- coling10-hillwalking
- ... bunch of other stuff
- inlg10-hillwalking
- ... bunch of other stuff
Now you want to revisit the hillwalking work. So you're too clear-headed about it because the midafternoon drowsies are sinking their hooks into you and you only notice one of the things marked hillwalking.
... and you spend the next week working on a piece of code that's at least one conference paper old until some voice in your head says "huh! I thought I made myself a diagram of this stuff. Where's my diagram?!" (and five minutes later "DOH!").
Good thing I was using darcs and could easily merge my work back together.
Good thing I was using darcs and could easily merge my work back together.
Revised scheme
Basically I think that Big-Endian is the way to go, and that when it comes to work that's somehow conference-related, the conference is not the Big End. The Big End is the thematic work which may be related to several conferences.
Maybe the scheme I should have used is
- ARCHIVE/2010-brighton/hillwalking-A-inlg10
- ARCHIVE/2010-brighton/hillwalking-B-coling10
- PROJECTS/hillwalking-C
And if I later on discover that this needs to be pegged to conference and I'm done with it, I can save it as ARCHIVE/2011-brighton/hillwalking-C-foo11.
Note that I'm using 2-digit years to denote a conference naming year and not the calendar year. So I'd say 2010 to refer to the year 2010, but INLG 10 to refer to the INLG conference that takes place in 2010. So you might see me with things like ARCHIVE/2009-brighton/project-A-acl10
The amount of thought I put into this must be a sign of mental illness.
