How do you organize development projects on your computer?

~
Code

• contribute <- forks
• deprecated <- archived repos
• legacy <- EOL repos
• personal <- my repos
• vanillaes <- org
• vanillawc <- org

Sites

• somesite.com
  • _assets <- raw images, etc
  • content
  • public
  • server

Work

• _assets
• work repo

I tried many complicated systems to separate by content type, language, platform, etc. They always ended up becoming aggravating over time.

Ironically, this more-or-less reflects the 'feature based' directory convention I use for web dev.

I aggressively curate this; as well as my GH repos.

I never fork a project unless I'm going to contribute to it or I neeed a custom fork. Custom forks should -- ideally -- be killed as soon as I find a workable alternative.

I don't hold on to forks of all the projects I've contributed to. Best case scenario, it becomes a big pile of outdated trash. If I want to look up something I worked on in the past, it's all recorded and reaadily available online.

I don't keep a collection of snippets either

My motto is...

"If it's not in production, it's not maintained. If it's not maintained, it's probably not worth using."

I'd rather master the ability to quickly and efficiently locate info on anything. Than be a master archivist of bit rotten code that only I care about.

Digital hoarding is still hoarding. I treat my local setup like a desktop. Keep it as free of clutter as possible so I have more (mental) space to work.

I have different folders on my C drive: ‘Projects’ for my work projects, ‘Side projects’ for my work related side project, ‘Personal projects’ for my personal projects and sonon. Each project has a root folder (named after the project) inside the allocated folder(e.g. Personal projects), which contains ALL the files related (git, src and other files) to that project (since I’m a web dev, it also contains the webroot of that site). Then every root project folder has a different icon (for clients it is the client logo, otherwise it is a related icon). Hope this helps you out!

I usually try to keep it simple. I have a Development directory with all the repos and projects. Sometimes I add another dir in-between for projects with more than one repo.
I usually navigate with terminal and I've oh-my-zsh installed with fuzzy completion, so it's enough to remember even a tiny bit of the folder name.

I keep all of my projects in ~/Source/ organized in the same way that they're organized on GitHub: ~/Source/${organization-name}/${repo-name}. Everything I work on ends up in a private or public GitHub repo, so this makes it simple to find what I'm looking for and to remember where it exists on GitHub. For temporary projects / scratch space, I put those under ~/Source/tmp/ and clear it out frequently to keep it from getting out of hand.

~/work/COMPANY_NAME/PROJECT_NAME

I use this pattern for everything. Primary work projects, consulting projects, personal projects, github forks, etc... Namespacing via company/user + project seems to cover pretty much everything I've encountered.

Zen on minimalism. I have 2 directories: projects for anything I work on and git for any repo I cloned to use. I try to name my projects smartly so the autocomplete works, and just delete any repo I'm not working on for a month from now, I can clone it again any time I want. Test projects are in ~/temp dir which is completely fine to be deleted, if some are crucial, put it in a repo that makes use of it.

I basically follow the GOPATH structure for everything because I like it.

I usually have an Engineering folder in my user directory, under that, folders for languages, under those, at least a "src" folder, under that, the root VCS name (e.g. - GitHub.com), under that, my user name at said VCS, under that, my repo names.

It feels awkward at first, but it's been the only thing that has stuck with me.

I keep a 'workspace' directory in my user directory so that work computer migrations will pick them up. It is then broken down by team name, with my github account name as a team. Everything fits into this for me. If you have too man (I only have around 20) then you could break down by various means such as language or framework.

I use ~/Projects as root for all my devops/web projects, like I saw in some other comments.

.
├── _archives
├── _forks
├── _sandox
├── _scripts
├── _tmp
├── ...
├── nicolas-brousse
└── pantographe

First folder (all who start without _) is always "organization" mainly its a client name. I do the same inside _forks that contain GitHub project I contribute. The inside an "organization" folder its the project name (ex: pantographe/website).

I also have a p alias to quickly go into a project.

p () {
    cd ~/Projects/$1
}

I try to take time to move older projects in _archives, then after some time, I move them to my NAS or delete them to free some space on my laptop.

Same here, actual coding is the easiest part.
Hardest part has always been setting up projects and keeping them organized.