Saving projects

[MisterX]

Shari,

Great insight!

I use a similar method, Im also the Space Manager in my company and we have
a bunch of folders, let me tell ya! 

Anyway, here's the variant, and an extra tip...
Consider that folder hierarchies can easily become very long in these
schemes so it's important not to repeat some info in folder names. Who
doesn't like long folders? Some backup software, copiers, Windows, DOS,
etc... 

We have a couple thousand people in our company. We have a business side and
an IT side. Each with about 100-150 different sections, each of which has
prod, testing, mgt, development, support and each sometimes with sub groups!
Talk about organization!

Anyway here's how it works at home... A + is a folder
+Projects
  +DiscreteBrowser
    +bkps
      +20041101
         stacks
         + folders of project
      current stack v.x.rev
      current stack v.x+1.rev
  + PropsN2O    
    +bkps
      +20041101
         stacks
         + folders of project
      current stack v.x.rev
      current stack v.x+1.rev

Backups are easily filtered and washed from the disk. 
Versioning is important to keep track of your changes. (see the history
section in any about box in the stacks of MonsieurX.com. It's helped a lot
in the past to see what happened! And it's nice to see features add up for
the features write up or the help.

This may not be for everyone but I've found this structure easy to manage
and navigate.

The dates are written in reverse so that any stupid program like the MS
explorer or DOS can sort them correctly. Doesn't happen the other way
around. You'd think that after 25 years PCs would learn a new trick eh?

What is nice also is that if you do a search in a backup or just the folder,
you can find all the changes per day or project. 

Good weekend to all!
Xavier




> -----Original Message-----
> From: metacard-bounces at lists.runrev.com 
> [mailto:metacard-bounces at lists.runrev.com] On Behalf Of Shari
> Sent: Friday, November 05, 2004 15:56
> To: metacard at lists.runrev.com
> Subject: Saving projects
> 
> We all know that you should save often when programming.  You 
> never know when you might need to go back to an earlier 
> version.  I learned a neat trick from an accountant awhile 
> back, and they are nitpicky buggers, accountant's are.  But 
> sometimes that's a good thing....
> 
> I frequently save my projects into a separate file, and use 
> the date as part of the file name.  I found that not having a 
> date in the file name and trusting the created/modified date 
> can easily fail.  If you open the file and don't do anything 
> and close it, it might show the newer date and throw you off.
> 
> For example, today's folder is called "BJG 11-5-04".  
> Throughout the day as I am working, I will save a copy of the 
> folder.  By the end of the day I will have several folders.  
> Each will have today's date 11-5-04, with a "Copy 1, Copy 2" 
> etc.  I look at the created/modified time for the most 
> current version on a particular day, rather than the "Copy 3".
> 
> At the beginning of a new day, I change the folder name for 
> the new date, making sure there is a copy first.  All 
> previous saves go into a "Saves" folder.  And as the days 
> pass, I will clear out the "Saves" 
> folder so that only that last save for each day remains.
> 
> I keep copies going quite a ways back.  Sometimes you need to 
> go back and review how a piece of code was written way back when.
> 
> Just one gal's methodology....
> 
> :-)
> --
> Mac and Windows shareware games
> http://www.gypsyware.com
> _______________________________________________
> metacard mailing list
> metacard at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/metacard
>