9 ms·
Funnily enough this happened to me. Earlier in my career I had a very intense, productive working day and then blundered a rebase command, deleting all my data
by willrftaylor 2y ago
Funnily enough this happened to me.
Earlier in my career I had a very intense, productive working day and then blundered a rebase command, deleting all my data.
Rewriting took only about 20 minutes.
However, like an idiot, I deleted it again, in the exact same way!
This time I had the muscle memory for which files to open and where to edit, and the whole diff took about 5 minutes to re-add.
On the way out to the car park it really made me pause to wonder what on earth I had been doing all day.
- thunfischtoast 2y agoSometimes you really wonder where your time went. You can spend 1 hour writing a perfect function and then the rest of the day figuring out why your import does work in dev and not in prod. I also once butchered the result of 40 hours of work through a loose git history rewrite. I spent a good hour trying different recovery options (to no avail) and then 2 hours typing everything back in from memory. Maybe it turned out even better then before, because all kind of debugging clutter was removed.
- BossingAround 2y agoSometimes, I spend an hour writing a perfect function, and then spend another hour re-reading the beauty of it, just to be pointed out how imperfect the function is in the PR review :))
- alex_smart 2y agoIn case you didn’t know, doesn’t delete the commit. You can use `git reflog` to find the commits you were recently on and recover your code.