Tell people you love them every day because you don't know when it will be the last time.
But more importantly, don't forget to "git push" every day, because you never know when your laptop is about to die, taking with him those last commits. RIP my friend.

The Phantom Push (any MGS fans)!

Whaaaat? Computers actually die?😲 I thought that was just the lie every hobbyist tells at least once to buy time on a side project he accidentally got too many followers for.

The independent project scene is overflowing with blog posts about "losing everything". It's become kind of a running joke how the worst thing for a computer is using it for something people are interested in.

They do die. And it's not the first one that dies in my hands. The first laptop had an HDD, which is doomed to die after a while because of the mechanical parts.

This new laptop was only 2 months old, and has one of those new SSD directly into the PCI. And still it died from one day to the next one.

DON'T. TRUST. ANYTHING.

Scary! Every computer I've owned since 1985 still turns on. 😄 I'm sure nothing will ever go wrong for me!

Don't run off yet @Lisanna, I have questions! I know they are not the same thing, but what do you mean by that? Like I should make backup of the code that is already hosted in a git repo?

@Lisanna I agree with you on losing the stash and untracked files, although I only use the stash to move between branches, and I would delete the content of the stash within a day. Also, commits should be atomic and simple enough and you should commit regularly (probably to topic branches available to you only), so even though you would lose work between commits, it's just hours of work, not days. Maybe I'm bold, but backing up seems so overkill, and I would have to do it constantly. You use Dropbox or something like that? To be honest you are the first person i know that backs up the project and uses a VCS at the same time.

@Lisanna I agree that a git is so much more than just a way to make backups. But in the other hand, a git repository hosted in a server is just a backup of your local git (more or less). In that way, you can have a de-centralized workflow and make use of git-push for backups. Taking your example of the Linux kernel, each maintainer have their own hosted git for backup and reference. Linus Torvalds even have a 3rd one in Github I think. As a developer you don't make pull requests (I think), and just send the patches through email, but that doesn't keep you from having your own hosted git for backup.
I'm not saying that you are wrong. I'm just trying to get your point. :)