Couldnt you just git commit more often?

[james-see]

It takes seconds to run the command. Not sure the necessity of this at all, and it may actually cause bad habits and behaviors that could lead to other sloppiness and waste in other areas of your life.

[JakeStanger]

One could go about removing most automations from their life is they chose to. My suggestion would be if you don't personally find software neccessary, and you do not have a requirement to use it, don't use it.

Just to be clear though, this is not a replacement/automation for git commit. It's using Git as a local backup tool.

[tkellogg]

I built the tool after wasting a day or so because I didn't commit often enough and lost my work. I suppose it's a matter of perspective as to what is more harmful. Given that a simple tool now exists that eliminates an entire class of errors/waste, it seems irresponsible to not use it, but that's just my perspective.

When presented with a failure, I tend to take a kaizen approach — rather than assigning blame, I try to find a systemic change that eliminates the possibility of the failure from happening in the future. It's why I like typesafe languages like Rust, they offer lots of avenues for preventing entire classes of mistakes. Dura takes care of an entire class of mistakes that happens infrequently enough that most people can't rationalize the time to automate a fix, but would gladly brew install a fix.

[chapmanjacobd]

You could do something like this every 20 mins -- or just run it before you do something crazy. But there are still ways where you could mess up your git index or your office could collapse. There is likely more assurance in pushing your code to multiple git servers located in different countries using Tower of Hanoi rotation

git add . && git stash push --keep-index

[cjrh]

When I was using Jetbains IDEs like PyCharm, they have a Local History feature that works in a very similar way to dura. It saved me countless times! In these instances for me, it wasn't about saving frequently, it's been more often due to getting a rebase or a force push wrong and losing work; often when working on multiple different computers. Sometimes you don't even know you've lost work until later when you're staring at the screen thinking, "I'm sure I already fixed this...". Now that I'm back in a vim-centric dev mode, I want that safety net again. I certainly don't want to commit more frequently to my actual dev branch, because I want to use the git staging index to control what goes into each commit. (Yes there are ways to redo the commits after the fact etc etc). I really like the dura model of working like backups and staying out of the way of the main repo.