Starting a code library.
- by Rob Stevenson-Leggett
Hi,
I've been meaning to start a library of reusable code snippets for a while and never seem to get round to it.
I think my main problems are:
Where to start. What structure should my library take? Should it be a compiled library (where appropriate or just classes I can drop into any project? Or a library project that can be included?
In my experience, a built library will quickly become out of date and the source will get lost. So I'm leaning towards source libraries that I can export from SVN and include in any project.
Intellectual property. I am employeed, so a lot of the code I write is not my IP. How can I ensure that I don't give my own IP away using it on projects in work and at home? I'm thinking the best way would be to licence my library with an open source licence and make sure I only add to it in my own time using my own equipment and therefore making sure that if I use it in a work project the same rules apply as if I was using a third party library.
I write in many different languages and often would require two or more parts of this library.
Should I look at implementing a few template projects and a core project for each of my chosen reusable components and languages?
Has anyone else got this sort of library and how do you organise and update it?
