One thing I find helpful to hammer home when helping coworkers with git issues is to hammer home the point that you cannot permanently lose your work so long as

One thing I find helpful to hammer home when helping coworkers with git issues is to hammer home the point that you cannot permanently lose your work so long as you commit it somewhere. Some things you might do will make it harder than others to find where your code is, but it's always (unless you run git gc) somewhere. Then, you demonstrate that you can make it trivial to undo what you did in git if you just take a branch off of every branch you're going to be messing with before doing so. IMO, a unified "git undo" would probably be a valuable feature for pedagogical reasons.