~/source

/dev/null

~/code for everything I want to change/look at the source code.

~/.local/src for stuff I want to install locally from source.

~/repo for code I write and ~/src for code I didnt.

~/gits

Documentation is usually a doc folder inside the repo or just a README.md for small projects.

For my personal projects I use ~/dev/projects/

For clones I use ~/dev/clones

My audio engineering stuff is at ~/audio/{samples, plugins, projects, templates}

~/dev

For a project called “Potato Peeler”, I’ll put it into a structure like this:

~/Projects/Tools/Potato-Peeler/potato-peeler/

Tools/ is just a rough category. Other categories are, for example, Games/ and Music/, because I also do gamedev and composing occasionally.

Then the capitalized Potato-Peeler/ folder, that’s for me to drop in all kinds of project-related files, which I don’t want to check into the repo.

And the lower-case potato-peeler/ folder is the repo then. Seeing other people’s structures, maybe I’ll rename that folder to repo/, and if I have multiple relevant repos for the Project, then make it repo-something.

I also have a folder like ~/Projects/Tools/zzz/ where I’ll move dormant projects. The “zzz” sorts nicely to the bottom of the list.

Any naming convention is fine as long as it’s meaningful to you. But it’s a good idea to keep your own repos separate from the random ones you clone from the internet.

Like some other ppl here, I clone everything in a git folder under my home directory.

~/src/ Simple, effective, doesn’t make my home folder any more of a mess than I already left it as.