Linux

When I change devices or hit file size limits, I’ll compress and send things to my NAS.

Whaaatt!?!!? That sounds like you don't use git? You should use git. It is a requirement for basically any job and there is no reason to not use it on every project. Then you can keep your projects on a server somewhere, on your NAS if you want else something like github/gitlab/bitbucket etc. That way it does not really matter about your local projects, only what is on the remote and with decent backups of that you don't need to constantly archive things from your local machine.

Similar question was recently asked here

Generally what I’ve seen work well in my career and is consistent across thousands of devs I’ve worked with: ~/[whateverFolderNameYouWillRemember]/[organization]/[project]

I recommend when it comes to finding things to just use a fuzzy finder, such as fzf.

I put stuff in places, then immediately forget where I put them.

I push every project I work on right away to my gitea instance. If I expect not to work on something for some time I just delete the local copy.

When I change devices or hit file size limits, I’ll compress and send things to my NAS.

Well, that sounds inconvenient.

Hosting my own git server on my NAS made my life easier and better due to the new freedoms it offers. Backups are centralized, and I have all the space i need to keep any interesting code safe. I am using forgjeo now and highly recommend it. You can also use other front ends (or none and just ssh/filesystem) but forgjeo gives me artifacts (ie docker registry), code search, LFS, and more. With my own git server, my local filesystem only has what I am working on recently (or as my workstation space allows). My home folder has a folder for each version control system (git, pijul, svn). Inside of these i have 2 sub folders: /

Some examples of different domains are: open, work, personal, dragonish. I do not separate what forge or remote service in the filesystem, this is a persona boundary.

I use git remote names and branches in each repo to handle what software forge and any upstream/maintainers i need to work with. As an example my work repos only get pushed to my work server (ie, only 1 git remote named origin set to my work's server), but my open ones will go to forgjeo and github (i setup 2 git remotes, origin and github. origin in this domain goes to my forgjeo). If i have a need i go into some more git branching strategy which I do find has helped me over my life, but I think I am overthinking this post now! keep it all simple enough for what your needs are.

I have a dedicated directory with subdirectories for each project and that's it

Everything is in git, and I tend to use IntelliJ as an IDE. So my projects are all in ~/Ideaprojects/[PROJECTNAME]

As an addition to your post, I'm also in the process of learning C/C++, and I'm curious also how others arrange their actual project files and include directories. Like, for example, if there's a bunch of classes having to do with UI elements, do you just group them each under their own file all in their own directory? I've also seen projects where everything was just thrown into the top level directory, both headers and implementation files together in a giant pile of source files.

I used to be put everything in ~/Programming at the top level. I later started grouping projects by type (JVM, Web etc.) in subfolders because it was getting hard to find things. This was synced with Nextcloud. However, I then at some point passed 2 million files (200GB) in said folder and decided to search for a better solution.

I ended up using a selfhosted Forgejo instance. It allows for easy code searching across all projects, tagging projects by topic and language, LFS, and has useful project management tools built-in.

I keep a root folder. On Windows it's in c:\something on Linux it's in /something

Under there I've got projects organized by language. This helps me organize nix shells and venvs.

Syncthing keeps the code bases and synced between multiple computers

I don't separate work from home because they don't live in the same realm.

Only home stuff in the syncthing.

${HOME}/Projects/(Personal|Work)/

If either folder gets to busy I start to create projects Meta folders that normally corospond with a gitlab group.

I just blow out the folders with a good ol rm -rf ./ And git pull if I want to mess with it again.

projects/[rust|cpp|python|..]/proj-name

• Keep everything in git. You can use third party services like Codeberg, GitLab, or GitHub, or host your own on your NAS.
• When you're not working on a project and don't think you'll need to reference it for a while, just delete it from your laptop. The code always lives in git anyway.

In terms of local storage, I usually have everything in ~/projects/project-name, and I don't have tiny file size limits because I don't use FAT32 filesystems — that's the default filesystem you usually get on USB sticks and external hard drives you buy. You have to format those drives to something like EXT4 (Linux) or NTFS (Windows) or you get stuck with FAT32 which has 2gb file sizes.

i use coding/languagename/project, where most if not all projects are git repos. so, coding/python/shira, coding/java/datetime examples i have some wildcards for the languages, most of my serverside js stuff lives in coding/node-deno and most of my fullstack webdev stuff lives in coding/webdev

i used to have the coding directory on a hdd, but moving it to an ssd helped a lot when installing things made with node, among other things.

I have a folder for my projects on root and within those projects I have my GitHub repos all contained within their own directory named the same as the project.

If I am learning something, I have a folder for the topic I am learning, and a logseq file with all of my notes. Then I have folders for my book references, one for video or audio references, and then a folder for my practice projects.

Whatever Cargo generates for me. If I use workspaces, then I put the subprojects to the root of the directory.

~/real

~/real/cprac

~/real/git

Devs who don't use git and devops properly are infuriating to work with. I'd recommend getting started with that ASAP.

On my personal computer ~/Projects/<name>, you need to remember that real-life is not like college, you won't be working on a new project every week. If you have more stuff than you can manage like this, you've bitten more than you can chew.

On my work computer it's a bit more complex, because I have to work with other people's projects as well, so I have a ~/Work folder and in it several folders by type of stuff, e.g. ops for operational stuff such as scripts to deploy stuff or grant permissions, code for servers (and client) code, etc. Also if I'm working on something specific that requires multiple repos I create a folder for that project with the repos inside.

I just have all my active projects under $HOME/projects/ and projects from other people in $HOME/bin/

I don't have many so I just put them all in ~/own_repos (as opposes to another directory I have for other people's git repos). Maybe if/when I have more projects I'll have a more elaborate system.