True, although ideally reflog is just a backup in case you make a mistake (and not an integrated part of your workflow). What I've found surprising is just how

True, although ideally reflog is just a backup in case you make a mistake (and not an integrated part of your workflow). What I've found surprising is just how different workflows can be from project to project (or company to company). Some developers are die-hard about preserving history at the expense of the graph, whereas others are straight-line purists (and don't even accept merge commits on the remote). I actually have some limited support for "git checkout -" to go back, but I should get around to making a legit reflog...