Chapter 9 of 9 · 3 practices · 2 min · 3-question quiz
Version control and backups for the report
Lost files and conflicting copies cause last-minute disasters every year. Keep one source of truth, track history and prepare the final submission package early.
Start: Keep one shared source of truth for the report3 practices in this chapter
- 1Keep one shared source of truth for the reportReports emailed back and forth as "report_final_v3_REAL.docx" are how sections get lost. Choose one place where the current report lives, agreed by the whole team: All three keep a version history…
- 2If you write in LaTeX or Markdown, keep the report in GitTeams already using Git for code can manage the report the same way. Split it so people rarely edit the same file: Commit small, meaningful changes with clear messages ("Add sync conflict results to…
- 3Back up in two places and prepare the submission package earlyLaptops get stolen, drives fail and power cuts corrupt files, usually in the final week. Keep the report and code in at least two places, such as the cloud tool or Git host plus a copy on a separate…
Check yourself on this chapter
3 questions, right here once you are signed in. Your progress is saved as you read.