Question Application Naming Conventions...

[ChristinaSeay]

Can anyone share any advice for how to handle application naming conventions in a multiple-developer environment?

Currently we've just been using incrementing numbers ([folder])
-- [1000]
-- [1200]
----- [V0]
----- [V1]
----- [Publish]
---------- liveprogram.exe
-- [1300]

But we've been debating switching to a system that includes a more specific name for a program that more aptly describes the purpose of the program.

 

[jmcilhinney]

Absolutely, you should always be using descriptive names for everything. In our office, we do assign a number to each project but we rarely use the number alone to identify them. If you use source control, which is a good idea even for a single developer but pretty much essential for a team, then you don't need to worry about separate folders for different versions of the same app. You can always get back to any version via source control. We use SVN at work, with a repository (essentially a root folder) for each client and then a folder under that for each project for that client.