I know I'm late to the thumb drive game. They've been growing in size and have become part of more people's workflow for many years.
It suddenly occurs to me that (to pick an affordable number) 64 GB is really a lot. Well structured, it's not just enough to carry current work, it can carry a very extensive portfolio.
So I have restructured my archives again, as is my hobby or affliction, and created a file structure called "time-machine."
I can keep 10 years of data on one, best practices.
=> More informations about this toot | More toots from John@socks.masto.host
What are our best practices?
I think it's really empowering to be able to decode any kind of working directory and extract your work, leaving behind other people's programs and frameworks.
For instance if you're using something like a python virtual environment, you want to note what libraries you've pip'd in but you don't want to archive them. Similarly if you're using a big IDE you probably do not want to just package its project structure. Those are far too bloated. Extract your files.
=> More informations about this toot | More toots from John@socks.masto.host
When I was cleaning up and reducing I found some really monstrous Arduino project directories. Monstrous even when each project contained only 100 lines of my own code.
I haven't used that tool recently, I don't know to what degree it has any kind of "package and archive" for projects, but I think such things should.
Otherwise people keep "needing a bigger NAS"
=> More informations about this toot | More toots from John@socks.masto.host
text/gemini
This content has been proxied by September (3851b).