So how do you organize your code projects?

[Bulldog13]

Hey all,

Does anyone have a comprehensive system for how they store all of their programming projects? Unfortunately, I have been using the defaults the IDE or tutorial gave me, so have multiple programming projects strewn all over my PC.

For example I program using Eclipse, Visual Studio, PyCharm, and Notepad++. My stuff is everything from AngularJS to PhoneGap to Django to JavaServer Faces to MS. It is literally strewn all over my PC.

I have a fresh development laptop now and do not want to make the same mistake, so was curious if anyone had a system for keeping projects organized and together.

 

[beginner99]

I'm nto sure I fully understand your question.

I don't have that many projects. I have 1 folder with all java projects in it. This folder is in "my Documents" (Windows). I have another folder for php projects which is also the document root of my XAMPP installation. This makes it easy to debug or quickly see changes in real browsers.

You could create an additional hierarchy by programming language or application type (web, client, service, library,...), by IDE you use or whatever else suits you.

 

[Train]

In each IDE, you should be able to specify what the default folder is to create new projects. Set all your IDE's to the folder you want all new projects to go into, and you should be fine.

 

[Bulldog13]

I'm nto sure I fully understand your question.

I don't have that many projects. I have 1 folder with all java projects in it. This folder is in "my Documents" (Windows). I have another folder for php projects which is also the document root of my XAMPP installation. This makes it easy to debug or quickly see changes in real browsers.

You could create an additional hierarchy by programming language or application type (web, client, service, library,...), by IDE you use or whatever else suits you.

Was basically asking this,

http://programmers.stackexchange.com/questions/14582/how-do-you-organize-your-projects-folders

 

[EagleKeeper]

Main directory called projects
subdirectory for the project name and/or customer. Use to contain documentation on project
subdirectory for the actual work that the IDE points to.

 

[smackababy]

Main directory called projects
subdirectory for the project name and/or customer. Use to contain documentation on project
subdirectory for the actual work that the IDE points to.

I am similar.

Main Directory called workspace
subdirectories for each project
subdirectories for each build, which is what the IDE points to.

 

[BrightCandle]

A have a git repository for most of the smaller projects split by programming language in my ~/checkouts directory. Then I have all my larger individual projects inside of checkouts directly. I import projects into my IDE's and leave them in place. That is it, no more organisation is really required and I have 50 ish projects like this.

 

[Markbnj]

A have a git repository for most of the smaller projects split by programming language in my ~/checkouts directory. Then I have all my larger individual projects inside of checkouts directly. I import projects into my IDE's and leave them in place. That is it, no more organisation is really required and I have 50 ish projects like this.

Mostly this. I don't really store my projects locally anymore. I have them on bitbucket and pull them into a workspace when I need them.

 

[douglasb]

Mostly this. I don't really store my projects locally anymore. I have them on bitbucket and pull them into a workspace when I need them.

I envy those of you who work at places that aren't a decade in the past and still stuck on centralized version control. Worse, yet, it's on a relatively old server that crashes frequently, which means nobody can get anything done when it crashes because we use TFS and have our policies set to where a constant connection is pretty much required.

I secretly pray that this server bites the dust one day, so the boss finally realizes what a mistake it was to have all of the source code for every client on a single, ancient, in-house server. Then again, this was a 100% VB shop when I started here, so maybe I should be thankful that we use source control at all.

 

[Train]

Mostly this. I don't really store my projects locally anymore. I have them on bitbucket and pull them into a workspace when I need them.

I like BitBucket, have just recently started favoring them over GitHub for my own stuff.

GitHub still better for finding OSS stuff as there is a much larger user base, but free private repos up to 5 users makes BitBucket friggin great. Not to mention I now think SourceTree > GitHub for Windows.

 

[Train]

I envy those of you who work at places that aren't a decade in the past and still stuck on centralized version control. Worse, yet, it's on a relatively old server that crashes frequently, which means nobody can get anything done when it crashes because we use TFS and have our policies set to where a constant connection is pretty much required.

I secretly pray that this server bites the dust one day, so the boss finally realizes what a mistake it was to have all of the source code for every client on a single, ancient, in-house server. Then again, this was a 100% VB shop when I started here, so maybe I should be thankful that we use source control at all.

I was using Visual Source Safe for a VB 6 project back in the 90's man those were the days.

VSS actually worked great up until someone forcefully broke a read only lock (cuz the guy who had an important file checked out went home for the weekend) Then you had a conflict, and it took brain surgery to unbreak the project, lol

 

[Markbnj]

I envy those of you who work at places that aren't a decade in the past and still stuck on centralized version control. Worse, yet, it's on a relatively old server that crashes frequently, which means nobody can get anything done when it crashes because we use TFS and have our policies set to where a constant connection is pretty much required.

I could probably work the same way using SVN or TFS as long as it was available over the net or using a VPN.