I am working on two different project simultaneously where whenever the changes are made we useTortoise SVN for project ABacked up by folder for Project B (this is done by me on my system)I find SVN good for maintaining the latest code server machine and update it whenever necessary.For Project A, I happen to make alot of changes to the project A and I am advice not to commit the changes again and again but just a major change all at once.But since in not alone on project A I tend to make code backs by folder every time I make an important change so I can go back and return if some conflict occurs.But what should I do in case of the project B?where most I am on the project (as of now).Should it be SVN or folder backups?The reason I do folder backups for the project B is thatsometimes the build given to the client fails/buggy so instead of making them wait for it to fixI just go and open the project and compile the last working build and give the executable so they can carry on their work and not wait for me to fix it (may take long).I am working with Delphi on both the projects.
confusion between SVN and code backup by month/date/time whenever i make major or important update to the code
version control;svn
im advice not to commit the changes again and again but just a major change all at onceIt's wrong advice.project B where most im on the project (as of now) should it be SVN or folder backupsYou should use version control in any project.Backups and version control are not the same thing, although an external  repository (centralized, or distributed in another computer) is a backup in itself, and backups (e.g. dated folders or zip files) together with some diff tool (e.g. WinMerge) could serve as a very rudimentary version control tool. But since excellent version control systems are available for free, there's absolutely no excuse not to use them.Of course, backups must be taken in addition to using a version control system.