An organisation with several different projects with different technologies can probably benefit from having a common code repository. Whether it is a J2EE or Mainframe or any code, most of the projects will need common code for example, "database connection code". I have observed in lot of organisations the same database connection code is been written by different developers in different ways for different projects using the same technology. However, the objective is to write code for database connection which could be reused by import of code from commom code central repository. I think it is not a new idea because in today's world there are so many open source libraries, projects which are shared on internet and can be imported into our project structures. But, the reason I wrote this article is to find out what could be stopping to take this approach in a organisation's stand point. I could list the below benefits of source code sharing for same technology accross projects which are very much basic: 1. A Centralised location for the developer to import the code into his project. 2. No need to duplicate the same code even though it is a different project 3. Gives a chance to always learn & improvise developer's ideas by way of enhancements to the common code which is a huge benefit to the organisation 4. A developer can compete with another to produce qualitative code(good & bad):-) 5. I think it is not an expensive idea in organisation's cost point of view, it is like any other version control system developers are given access permissions depending on need.
If any body is thinking in the same lines, please keep me in the loop. Also, i hope I have posted this in right place.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus