Saving projects

[Ray Horsley]

Nice idea, Shari.  Thanks!

Ray Horsley
Developer, LinkIt! Software


On Friday, November 5, 2004, at 09:55  AM, Shari wrote:

> 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
>