Re: Knowledge for a basic programmer and advanced programmer
Rob Coops <[email protected]> Fri, 12 Jan 2024 11:16:58 +0100
| Newsgroups | gmane.comp.lang.perl.beginners |
|---|---|
| Message-ID | <CABPR7FHib-TDs5YFQKLKPsW=c7u6Wtjhxbx5YMovd-vKY_cMFA@mail.gmail.com> |
I totally agree with John, backing up every whatever time frame is not a bad idea of course if you are creating documents and the like it can be very very useful to make sure you have a backup of those documents that you deem important. But when you are writing code you really need to get with the times and use version control. It is very simple to use and it allows you to not just have a previous copy of your code but also add comments to each version of your code so you can for instance explain to future you that this version is where you added feature X and the next version was where you greatly improved feature X and started work on refactoring that other thing. When you are a bit more comfortable with version control you get into branching and find that you can for instance have version 1.x of your code in one branch so you can easily make patches and rollout security fixes on that version while you are in another branch working on version 2.0. It is also indispensable when working on a project with more than one person (that is how pretty much all code is written in a professional setting) as multiple people can work on the same codebase without getting in each other's way. A very simple intro into the use of git you can find here: https://product.hubspot.com/blog/git-and-github-tutorial-for-beginners Whatever you do, please do not waste your time making infinite numbers of backups without any explanation of what makes this backup different from the previous 10 or the next 50. It is a pointless exercise. On Fri, Jan 5, 2024 at 5:04 PM John SJ Anderson <[email protected]> wrote: > > If you are coding you should be backing up every > > 10 minutes or more often. And you should store > > a "historical" full copy of the code every 30 minutes > > or more often and save them for days. > > No, you shouldn’t, because it is no longer 1985. > > You should learn how to use version control; the de facto standard at this > point is Git. > > j. > > > > -- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > http://learn.perl.org/ > > >