10 ms·
My opinion is that people tend to overdo solutions for problems like these. If you're not faced with some case where you're flashing a laptop on a regular basis
by Waterluvian 7y ago
My opinion is that people tend to overdo solutions for problems like these. If you're not faced with some case where you're flashing a laptop on a regular basis, don't aim for 100% coverage on your settings.
1. Figure out what files really aren't easy to replace (eg. vscode config, bashrc, etc.
2. Make a dead simple script that copies all these files/directories (and the script itself) to a temp folder and makes an archive of that folder.
3. Email it to yourself.
4. Make a `/remind me to ....` on Slack or an email service to remind you every few months to do this.
When I do recover, I don't just copy and paste all the files in. I use them as references as I rebuild. Because after a few years, my configs are filled with obsolete cruft or there's better ways to do things and I'll notice it when I go to paste in that segment into the bashrc or whatnot.
This certainly isn't an approach for everyone. Lots of people will want a more nuanced automagical approach. I just often find that over-automation just becomes this expensive headache that never ends up paying for itself.