I put everything in Dropbox including all of my projects. In my experience it works pretty well even if node_modules can't be ignored now.

Putting every projects in Dropbox with .git is the most awesome feature of Dropbox. With Dropbox's History and Time Machine feature, you will be almost never able to delete/overwrite your work permanently, even by intention.

Why not just use github, gitlab or other VCS? Personally, I enjoy using Dropbox for music projects (which VCS are not well suited for), but for code...

(I apologize if I sound as if I'm telling you what you should be doing; I am really just trying to understand the motivation behind such a decision - but I fully understand that even if something seems bizzare to me, it's just my personal humble uninformed opinion).

I don’t do as the parent does, but I’ve thought about it. The main difference is that a remote repo still requires an action to achieve backup parity. Using Dropbox your changes would start syncing the second you type :w. So even if you don’t finish the current development thought-line and commit upstream, you’re still backed up.

Still not sure if it’s a good idea or not, but not being able to ignore node_modules was the real blocker for me before.

They're completely different tools with different benefits, and both can be used together. VCS remembers only what you commit and push, per-project. Dropbox remembers your entire workspace as a whole, automatically. It remembers every time you save any file (more detail than you usually need, but can be handy in an emergency). It also remembers which projects you have on the go, and how they're organised. It remembers all the unpushed stuff within each project, including uncommitted changes, stashed changes, experimental branches, gitignored notes and ideas, even the knowledge of which branch you are currently on. Your entire workspace. And by 'remembers', I mean it automatically syncs all that stuff to all your devices, so your workspace is always exactly as you left it, whichever device you're now using.

>Why not just use github, gitlab or other VCS?

You can only revert changes to states that you have explicitly stored and uploaded. Dropbox does that automatically any time you save a file. That simplicity makes it more reliable. You will never lose anything you saved. And with rewind you can go back to any point in time. The advantage of git comes from its branch/merge features. But for a single developer on a small project that doesn't know git well that's not worht the complexity.

I moved my notes folder to git after having conflicted files for the upteemth time from Dropbox.

Two things that keep everything in sync:

1. Every two minutes my notesync.sh script runs, which basically does git add --all;git commit -am "New commit";git pull;git push.

2. Vim with AutoSave.vim which saves the document as I write.

Yes, there are a lot of commits, but I don't have to worry about losing anything.

Sharing your work with other companies where sales/marketing people need to have access to since they have no clue how to use Git.

After an office break in and having my laptop stolen my company gave me dropbox to back up my home folder.

Dropbox actually managed to completely hose every single node_modules folder by the end of the week. It got confused somehow then ended up just splitting all the files up with dates on them as if there was a conflict across hundreds of files.

Stopped using it after that.

Your company didn't have backups until it had a break-in?

I actually do this with my hobby .NET project and OneDrive. It's really a lot nicer when bouncing between two desktops and a laptop when I only have a half hour or an hour to work on something - everything is just there, and I don't have to futz around and check if I need to git pull, or worry if I get interrupted and don't get a chance to push whatever I'm working on.

Of course, NuGet is far less promiscuous than node, and I'm playing with a desktop app, so there's a lot less ephemeral stuff to have to sync.