How do you organize your projects?

twitter logo github logo ・1 min read

I've been working on a lot of side projects or small apps lately, and I feel like they're all just scattered about - between Codepen, Glitch, Netlify, my own webhost, etc.

It's made me wonder how other people organize or keep track of their apps, and what the best way to kind of "clean up" after myself is!

twitter logo DISCUSS (24)
markdown guide
 

One big folder for everything. In there I have 3 main structures.

  • All active, important projects get each their own folder.
  • All tests, small projects, and other small stuff go in one big “Lab” folder.
  • All the completed or finished projects, and also the abandoned projects (or as I like to call them, “Life Lessons”) go into yearly collections/archived. Then, if I’m trying to find an old exercise or a project made back in X year, I can go in and search for it.

What I like about this system is that it allows me to close any projects that don’t spark interest any more or that I finished, and as my main priorities are always visible first, I can focus on more important or relevant projects. I like to forget about projects, and then dig them back up with new eyes, to continue working on them; so I really like archiving what didn’t work and what I’ve already shipped.

Oh and even though some projects have their own git repositories, the whole parent folder is backed up to the cloud constantly.

 
 

Yay! I’m glad. It’s a system that works for me and ~5 years of design and dev projects, tests, exercises, courses, and crazy inventions. I would make a post about this, do you think it would be interesting or useful for other people?

 

I try to go fairly flat with my folder structure. One big folder called dev, which covers pretty much anything. Each folder therein usually maps to a git repo.

 

Same approach. My folder is named ~/projects/ instead.

 

I use GitHub to store and organize my code i have a main branch and three test branches i use to test multiple ideas simultaneously. to test builds i use circleci and azure pipelines. to keep stuff organized i pin the repos i am working on and create projects and reminders in azure boards to keep me organized and up to date. make note and reminder with onenote, evernote , or something similar to keep track of what needs to be done and how to do it. also clean out unnecessary commits and TODOS. hope this helps!

 

By level of seriousness:

  1. Folder on desktop (let's try this idea)
  2. Folder in Dropbox (I think I'm keeping this)
  3. Local Git-Repo in Dropbox (This is going somewhere..)
  4. Private GitHub-Repo (LET'S DO IT)
  5. Public GitHub-Repo (Rarely)
 

I develop using virtual machines so everything from a project goes inside and doesn't mix with others.

 

Do you have any example like screenshots? I really need these kinds of environments.

 

I don't know if screenshots would help much. I use Linux as my primary workstation so I just did some googling to figure out how to install KVM(Virtualization software) then downloaded Ubuntu and installed it. I do my work inside the graphical environment with whatever tools I need at the given moment. doing it this way I start with a clean slate every time.

one thing that does make it faster for me is that I created a virtual machine with all my most common tools...editors, browsers, compilers..etc and then I just clone it when I am setting up a new project.

Let me know if you get stuck on anything and I can try to help you through it.

Thanks :) I decided to use GNOME Boxes.

I installed it :)

I didn't want to deploy my projects to my machine.

Did you use it? If so, how can access a virtual machine IP from my machine.

Thanks :)

I have not but it looks to just be a front end for kvm. If you type ifconfig in your virtual machine you should be able to use the address to access it from your host machine.

 

Hi Desi, if this makes you feel better, I have a collection of projects spreaded between GitHub, Gitlab, different machines at home, pen drives... And some place I don't remember

 

I have a below structure for managing my projects and resources:

workspace/
workspace/ebooks
workspace/projects
workspace/projects/personal
workspace/projects/experimental
workspace/projects/[projectName]
workspace/documents
workspace/ui
workspace/ui/icons
workspace/ui/images
workspace/tools-software

 

I use a system I developed around 2008 that has been working ever since: organize all versioned projects under ~/vcs/, and reproduce the trees in real life hierarchically by version control system and service, thus:

  • ~/vcs/git/github/DavidLiedle/polyglot-test
  • ~/vcs/git/gitlab/DavidCanHelp/whatever-private-repo-is-here
  • ~/vcs/hg/bitbucket/DavidLiedle/projects-from-2011-2012 :D
  • ~/vcs/svn/omg/lol/projects-from-waaaay-before
  • etc...

This doesn't track what I'm planning, working on, or putting off for awkwardly large portions of a given decade, so for that I create PivotalTracker boards. I treat every project like a company, and the ones that get 86'd go into an _archive folder within their respective trees. I use DynaList ( dynalist.io/ ) to keep a birds-eye view of everything, and AirTable to get really granular with larger sets of information I need to correlate to a project. That helps me remember to follow up on CodePens, Glitch's, etc. Not saying I actually do follow up on them... It's not for lack of having them close at hand, though. :)

 

In all computers I work on there is a projects folder in the user's folder:

# Linux Mint

/home/cesc/projects/

# Mac

/Users/[macuser]/projects

Then, I'd usually add a folder per project and as time has passed, many of them have been grouped into bigger initiatives named after two fictional companies I own ~/projects/devaspros-projects/, etc.

Every project would normally have a github/bitbucket repo. Even smaller ones. I never miss a change to practice git commit often.

In the end, those projects are used to be showcase when applying to other companies or to show teammates how something was done.

Finally, I also find myself making a Trello board per project to organize tasks, paste links for concepts/answers/solutions while working on those tasks, and comments to myself. Kind of a self-documented process.

 

I think you can use tree structure to organize your job which it helps you find the project easily

Directory:

src/codepen
src/glitch
src/netlift
src/webhost
src/content
src/project
 

Everything goes into a git repo on GitHub, public or private, and get its own page in Notion.

If it's client work I tend to use Azure DevOps which used to be called Visual Studio Team Services (VSTS) which was basically an online version of TFS (Team Foundation Server).

Yay history lessons.

 

What I'm trying with my blogging is carry a little notebook and have a couple pages reserved for each side project or blog post, like so I can write ideas related to each one as they come and later turn them into Trello cards or outline items. I'm just starting this though so not sure how it'll go but I think for me the hard part with getting ideas is figuring out where to put them, so I'm hoping this would help with that

Classic DEV Post from May 6

The state of GraphQL

The report about the state of GraphQL base on the partial data gathered during the annual "The State of JavaScript" survey

Desi profile image
she/her. bug hunter. UI/UX copywriter. I want to make the internet more usable and accessible.

DEV is a social network for software developers to level up their craft. It's free and it's fully open source.

Sign up