Hello guys, welcome to another one of my blogs, after a long long time.
Today, we will look at how you can organize your project, because I have ran out of ideas, maybe I should buy a levenovo ideapad to get some, let me know.
So, the first thing thats absolutely neceseary is to have your projects all in one directory. Creating your projects(atleast the source files) everywhere across the filesystem is a bad idea, not only because you can't easily delete all your projects at once when you decide to become a farmer, but also because when you decide to migrate drives, good luck with finding the projects. The only exception for this should be when you don't plan to save nor reuse the file, in which case you shall position it in the /tmp/ folder, but because that ones messy you can use a subdirectory inside /tmp/, such as /tmp/Projects.
Next, you have a big decision, you can either leave all your projects in 1 directory, or organize it furthurer, by purpose, if you gave up on them, or by language.
Example of this may be:
./Projects/GaveUp/PortFolio  (don't have anything hard to put on there)
./Projects/GaveUp/Website    (because css sucks)

./Projects/GaveUp/Kernel     (easy)
./Projects/Active/Game       (easy)

./Projects/Stalled/AIWrapper (stalled cuz you don't have the 3 h100's you'd need)

Now that you created your directory inside directory for all your projects to be organized, its time to actually make this a Project database, not just a boring directory with nothing inside. So for example, you can write a script that will put an option to add a description to all your project, like you can see above.

Next, some obvious things: 
      - When doing version control via FTP(because you are too much of a chad to not use git), you should always put the tar files right beside the project source files, so its difficult to see whats going on, and when taring the current don't forget to also include all the previous version tar files into the current one, so the project will eventually become so giant and recursive you will just give up. [[citation needed]]
      - One thing you should isolate from your project source files is cloud keys and other security thingies, which you should store in a secure location, e. g. ~/.aws, or for ssh keys ~/.ssh
      - You should always include files like .clangd, .clangd_style or .local_variables.el in the directory with your project(assuming its required for the project), that way people don't have to create it again to use it.
      - For vibecoders, always isolate the directory your agent has access to, so he doesn't delete your other Projects with no value.
      - And at last, don't forget to vary the capitalization of all letters in the readme.md, examples may include: README.md, README.MD, readme.md, readme.MD, ReAdMe.md, rEaDmE.md...