How do people handle code names for their projects?

Question

We recently started using some code names for several different types of application prototypes following the topic. It made things a little more fun and was a great idea.

The problem is that I'm not too sure how people deal with the transfer of the code base from the "code name" state to version 1.0 state, which can have its own name ... not that the client really does not see :)

We are using Visual Studio at the moment, and I see that you can change the assembly name, but there are links to namespaces, etc ... this will really be a big change.

Are people really worried about changing things like namespaces before v1.0?

Answer 1

I prefer to change all links, including project names, folders, namespaces, everything when the real name changes. It may be a little painful, but it is better in the long run, especially when new developers are introduced to the project and are not familiar with the story.

Some companies continue to use code names within the company even after the real name is determined and released. Even today, there are places where "Opus" appears in connection with Microsoft Word (when information about the window handle is being digged, and not any published api or ui).

If you keep the code names around, you get a mess and a large document to know what's what.

http://en.wikipedia.org/wiki/List_of_Microsoft_codenames

Answer 2

I have always considered the names of developers to live in a different space than the name of the supplied product. If the development name is not profane or you create libraries or APIs, I do not see the necessary harm on the development name appearing in the symbol table or sumptin '. (In any case, your clients will generate their own profanity for your code;)

Sam answer agrees with this position, if the names of the developers never went beyond the code pit, there would be no Wikipedia page in which they are listed.