Is it necessary to use Git for version control when one person completes a project from beginning to end?

I haven"t been using Git for a long time. usually when one learns by writing a project , he feels that using Git for version control is a bit of a waste of time.

do you usually do version control when you write your own projects? And why?

Git
May.28,2021

Yes, some editors come with git versioning tools and are not particularly time-consuming. I usually submit a version after completing a main module. It's not just your own code that can go wrong. The demand may also change, and when the demand is changed, it will be better to fall back.


this is a problem of work management habits. A project done by a person can record git as a project log, which will be troublesome for people who are not used to keeping a log, but for those who have the habit of keeping a log, it is almost impossible to use GIT membership fee time, which is necessary.

I think the habit of logging is necessary for software development, so GIT is also necessary, no matter how many people work on the project. Maybe it's not necessary for you to use GIT, so you should also develop your own logging habits, otherwise you will seem out of place when you join the development team in the future.


of course there is a need. No one can guarantee that this thing suddenly wants to be changed back. Right. Can you ctrl+z what I just changed. I changed it a month ago. How do you find it?

with Git, one backup a day. You can also force yourself to write a summary. One function, one version. I want to use that.


you don't think it's necessary, waste time, don't use it, if the tool is your encumbrance, why drag you down.
Learning, it is necessary to minimize the cognitive load, the focus is on the project itself, and everything else is secondary.
wait until you feel you need it, and when you have the need to use it, it's not too late to use it. It's just a tool. It's not about getting a wife. If you don't marry now, you won't have a chance in the future.


it seems that your understanding of version control and the use you use in your work is not deep, whether it is a person or a team, there is no doubt that version control is necessary. Not to mention the benefits of multi-person collaborative development using version control tools. Briefly talk about the benefits of one-person development and use.

  1. develop according to module function. If a module is a version, using version control tools can help you manage branches
  2. if you have currently released a version online, and suddenly there is a bug, that does not use version control tools, you will only find the reason for the emergence of this bug, solve it, and go online again, but this is a relatively low-level and chaotic
  3. .
  4. if another person takes over the code you write, I don't know how many times that person has scolded you
  5. .
  6. it doesn't hurt to use more version control tools, what if one day your development is collaborative with others?

1, easy to trace history and roll back
2, removable USB disk
3, backup
4, people can't avoid collaboration, so consider it as learning
5, devops, continuous integration, etc. all need git and other tools


1. Every time you add new features / fix bug, you can feel free to do it boldly, but fall back
2. For others to take over your project, you can see the historical progress of the project by looking at the historical submission. Of course, commit log should write well
3. As learning Git
4. It is better to switch from push to server, and the working environment can be switched quickly


is a little bit necessary.

when you write your own projects, you often have a flash of refactoring framework and so on.

if you have Git, you can just open a branch and spoil it. If you don't have Git, it's troublesome to make a backup.

if it is really a very micro project, of course it doesn't matter, the version management that comes with the development tools is almost enough.

< hr >

it is said that webStorm and other things have their own version management, and it is not troublesome to download a graphical Git, and finish writing a commit every day


Yes, I wrote the wrong code, and I can get it back. If there is a problem with the online service, you can roll back quickly.

to the end? No one is clear about the future


Yes, you can not only save code, but also work across platforms! Or what? Do you have a flash drive? So terrible!


at least have a backup.


I don't know if it works, but a buddy of mine told me yesterday that he covered all the server and offline code, and didn't do version management.
ha
Maze


if you have more than one computer, it is necessary. For a single station, look at your personal habits


you must have it, there's no need to say that. Live with a sense of ritual, and so do writing code.

Menu