Telling people I don't need GIT and prefer to do things via FTP for years. That is till today when I accidentally deleted everything.

sudo apt-get install git

A year ago, I was there where you are now.

I still prefer ssh.

@devRat how did that work out for you?

@aplp I never looked back since git. I don't have to take backups of the files manually anymore.

@devRat but isn't the development process slower because of, well, git add --all . && git commit -m "some typo I just fixed" && git push -u origin master? And like, doing that, a lot? Whereas with FTP it was just a ctrl/cmd+s, depending on what editor one uses.

I only commit big changes to git.

@aplp you don't have to push after every commit and it's a breeze working on a team with it :)

@aplp It is very helpful even for small codes. When I was building my website I accidentally removed some js code that I got back from Git. Also, the commit messages are very helpful when you're looking back at your code months later.

To be honest, why you did is still better than CVS. Dear god CVS is awful; only s couple of months after I came to the company, a coworker and I convinced management to switch to Git and everyone's been happy ever since.

this is why i handwrite all my code in my journal

git is King

you masochist you😂

I use git but I'm very basic at it. Let's put it this way, I pity the soul who ends up having to share a repo with me. I mainly use it for work continuity when switching machines.

Even if you don't want to commit and push all the time, git is already worth it because of tags. With a single command, you take a compressed snapshot of your code base for archiving.

@aplp like @azous said, git is designed to help you keep track of changes both remotely AND locally. Often I write a piece of code, confirm it works, commit it locally. Repeat this until a feature is complete, THEN push it up. There's no need to push up often unless you think your computer is about to die or get stolen.

@Heatstreak nope, a lone wolf, rather