/s/p/
I made my project base folder path as short as possible. This reduces noise in error output, etc.Also lots of people blur their username from pathnames in screenshots. No need to do that.
'p' is short for projects
's' is a drive partition used for local copies of data synced to cloud storage (Dropbox, Google files, etc). Can be backed up less frequently.
I use https://www.insynchq.com to prevent folders like 'node_modules' from being synced
~/build/projectname/ for things I've downloaded/cloned for reading or compiling.
I generally consider ~/build/ to be ephemeral and it gets deleted whenever I build a new PC or start running out of disk space.
~/src/* gets moved to ~/src.old/ roughly once every five years, just to keep things fresh. Both are still backed up.
For example:
~/Code/codeberg/beretguy/foo_group/bar_project
~/github when I promote a messing around project to something i want to work on.
Same structure on Mac, Linux, and Windows (except I'm in %HOME% on 'doze).
If I have an upstream branch I tend to do
~/code/GitHub/reponame
Or
~/code/GitLab/reponame
Depending on where it’s hosted.
/Users/userName/Developer
Windows:
C:\Users\userName\source
If you name a folder 'Developer' in macOS, it automatically adds a little Xcode-stylized icon.
/a1 is "archive-disk number one":
/a1/comp is where computer code/information/manuals/etc is stored:
/a1/comp/j_wrk_master is where inactive code projects are stored indefinitely
If the project needs to be worked on again, the '/a1/comp/j_wrk_master/projectname' folder gets moved back to become '~/wrk/projectname' again.Rinse and repeat.