If you’re someone who regularly develops software, sites, or anything with any code, you’re going to start using source code control at some point.
And when a project ends, you’ve got options when it comes to maintaining the source code:
- Perhaps you’ll hand the code over to the client, and you will retire it,
- Or maybe you’ll continue to maintain it for the client as part of an ongoing relationship,
- Or there’s a chance you’ll be done with the project but still want to hang on to the source code.
For me, I’m partial to the latter option primarily because I like to have an archive of the things I’ve worked on throughout my career (no matter how trivial they may be) and because I’m a bit of a packrat when it comes to things like this.
Because if a client ever comes back for future work on a project, then I want to be able to spin up a copy of the development environment so I can get back to work. This assumes that I have an archive of the source, though.
But this assumes I have a repository archive.