Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
neeno3141288dI always push my changes, max time I stay without pushing stuff is a week. I'm glad you could recover your files, now you've learnt to never forget to push XD
matt-jd668288dThat's Why I usually do an end of day push if nothing else, saves you these kinds of heart attacks
homo-lorens6560288dAlternatively, that's why you always have a bootable linux pendrive ready, even if you despise Linux for some reason.
Fast-Nop32774288d@Lor-inc Agree, I can recommend Knoppix for that one. At least you can read all the files without permission fuckups.
And apart from Git, I'd also save snapshots on two local USB sticks in regular intervals, and attach the sticks only during saving.
cb219764288d@Lor-inc I had an extra hard drive for linux that I didn't use anymore, which wasn't so important. I chose that to override with a backup image. Turns out I'm incapable of using it to clone my drive, so it was all for nothing.🤦
General takeaway: I'm incompetent when it comes to using backup files overall.
I don't use Linux because I don't like the user experience for multiple reasons. Let's not start a flame war here...
TheCommoner2821921288dI usually try to keep git commits as small as possible. But that's not always possible. Sometimes the application does not compile if you don't change a lot and you couldn't use git bisect. So, if I have multi day commits, this is my workflow.
git checkout my_personal_branch_my_name
git add .
git commit -m "tmp_commit"
git push -f
And when I start working again:
git reset HEAD^
You have to have a branch where only you work. You force push over the last branch. Make a tmp commit over everything. And then remove it again.
Alright, dangling files of stuff you didn't want to commit. That's a problem that did not become a problem for me, yet. I try to write my .gitignore files first. But I am sure there is a solution for that, too.
homo-lorens6560288d@cb219 I didn't mean as a daily driver. But when you need to recover months of work, UX is less of a concern. I recommended it because I have yet to see a disk that isn't encrypted or physically broken and I can't mount it after 3-4 hours of shooting in the dark with data recovery tools.
Fast-Nop32774288d@cb219 Even when using Windows only, it's a good idea to make disk images. Since I'd never trust a disk imaging solution that works from the disk under backup, Windows based solutions seem fishy.
So a live Linux distro using Clonezilla is a good options and saveguards against disk failure as well as total Windows fuckups. Clonezilla is pretty easy to use with its wizard-style UI.
furryronin18Small agency, wants to try out some voice tech. Bought a Google AIY to get started, found some limits, worked ...
goddessofbugs3Best way to waste time: Debug the wrong thing. :D
lojigh2As we may all messed up a (git) repo at the begininng, do you know the surge of adrenalin right before pushing...