Late to the party here but this is the answer. Its clear from the summary that you filled a system with badly named files in any folder you could find. Thats the only possible way that "files from the 90's" are getting in the way. You ruined Bob's system and setting up a new one wont fix the problem.
My suggestion, is to mandate the strict use of ISO 8601, yyyy-mm-dd and use it as the prefix for all files. Set your file browser to descending order and you'll always see the most recent files first, in a format more visually easy to parse than Macgrrl's suggestion of just yyyymmdd. Delimters people, use 'em!
Anyone, even board members, that violate the file naming convention, send them down to Bob for a swift kick in the ass. They are the people that broke that last systerm, let Bob break them before they can do the same to the new one.
Poor bob. Built something good, somethign that last and a pack of jackals fuck it up and accept no blame for its ruination.
Slashdot Mirror
Late to the party here but this is the answer. Its clear from the summary that you filled a system with badly named files in any folder you could find. Thats the only possible way that "files from the 90's" are getting in the way. You ruined Bob's system and setting up a new one wont fix the problem. My suggestion, is to mandate the strict use of ISO 8601, yyyy-mm-dd and use it as the prefix for all files. Set your file browser to descending order and you'll always see the most recent files first, in a format more visually easy to parse than Macgrrl's suggestion of just yyyymmdd. Delimters people, use 'em! Anyone, even board members, that violate the file naming convention, send them down to Bob for a swift kick in the ass. They are the people that broke that last systerm, let Bob break them before they can do the same to the new one. Poor bob. Built something good, somethign that last and a pack of jackals fuck it up and accept no blame for its ruination.