Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm on Linux and use primarily command line tools for development, so I often go the path of least resistance.

I use Go quite a bit, which expects (well, not as much anymore) everything to be under `GOPATH`. Instead of messing with build scripts setting environment variables, I just set my GOPATH in one place and use a tool to check out specific versions of dependencies. It's convenient to set `GOPATH` to be my home directory, so my code projects (even non-Go projects) live in `~/src/...`, and documentation lives in each repository.

For personal stuff, I use:

- Documents - tax returns and other important docs - Pictures - screenshots and other mostly-worthless images - Downloads - anything temporary; gets cleared out periodically and serves as my "temp" dir - dot files for configuration (I don't back these up on a repo or anyone, I manually copy the 5 or so files I need) - network share - anything large or somewhat important that only gets accessed occasionally (ISOs, family movies/pictures, etc); rely on RAID to protect it - large HDD - games, VMs, and other large data that's not very important - a few directories in my home directory

Documents and a few random directories get backed up off site (tarsnap), and the rest is on code hosting (mix of BitBucket, GitHub, and GitLab).

Things are somewhat orderly, but not really well thought-out. For anything that the system uses, I put it wherever the system expects it (~/.local, /etc, etc). I don't worry about it too much, and I try to purge useless crap every few months (usually aim to delete a few gigs at least, which is usually a few hundred files).



That whole GOPATH thing is the reason I could never stick with Go. I'm curious to learn how it's less invasive now. Thanks for the heads up.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: