I’m currently writing some general purpose .net libraries that contain usual helper classes.
For example, to deal with string encryption/decryption, saving to configuration files, etc…
Right now, I’m the sole developer of the company I’m working in, and it doesn’t look like it is going to change soon: so I wouldn’t “steal” anybody code.
However, it is likely that I would leave the company at some point.
Like most developers, it is more than likely that I would like to reuse these libraries that I would have built over time, in my new company, since they would contain company-agnostic code.
If I name them after the current company, I will need to change the namespace and recompile all the new libraries, which may turn out to be time consuming and error-prone if there is a significant number of them.
I would also want to use these libraries for some personal projects and extend them during my spare time as well and working on those projects.
Naming them after my name though seems very egocentric though. If I joined a new company, I don’t think I would like to have the name of the previous developer in almost all the code files.
On the other hand, something like “Common.Library” seems a bit too generic.
I would like to know how you developers changing companies relatively often are tackling this?
Being the sole developer, I’m very flexible regarding the code-design decision but I would still want to respect the best practices and provide a decent code-base for my successor.
PS: I have checked regarding IP with my boss and they don’t mind as long the code I’m reusing doesn’t contain business logic, so please keep the comments/answers technical and not legal.
There is no general answer to your question.
Why not just use your initials, if you don’t want your full name in the libraries?
Something like
kd.Common.Library.