Don't Use the Source Control Tool As a Backup Mechanism |
 |
 |
 |
| Written by Graham Stoney | |
|
Your development machines should be backed up to prevent data loss. Engineers shouldn't check code in on a daily basis just to be sure that it doesn't get lost if their hard drive fails. They should check it in when the logical change they are working on is complete and it's ready for other engineers use. The time taken for a single logical change could be anything from minutes to months, depending on the scope of the change. This means that significant work could be lost if the developer's local work area disappears due to a hard disk failure. The solution is to back up your development machines nightly. If they need to check in an incomplete change to share it with other developers, they should do so on a branch. Social Bookmark this page:         
|