Code Reuse

Background

Code reuse is not a new idea but moving it into a code repository is a new concept. Code reuse has been a practice for developers since it can be more effective, has fewer bugs and has been tested in previous versions of applications. If code is used on one application and then another application has the need for the same type of action or event then the code can be reused if other developers know the code is available (National Instruments, 2010). Since the code has already been tested, consolidated and meets the organizational standards the code should be reused. The more the code is reused and tested the less probability for bugs or errors (National Instruments, 2010). If code is reused it may also benefit the user since the action or event will be familiar. Researchers will enjoy new features but will also identify with familiarity that will help with improving research. Since developers already reuse code, the next logical step is to build a code repository.

When a developer is writing code for an application and they are able to find code that has already been used and tested, it will reduce the risk of error and speed up the development and research process making an efficient process. The risk therefore is not in the code that is reused since the probability of bugs or failure will most likely be in the new lines of codes so it will be easier to find the errors (National Instruments, 2010). It is important to find a place to store and use code in an area that all developers can access. A repository would be an efficient place to store the code. The repository can be a web application frontend with a file server backend or database backend. This can be secured so only authorized personnel can access the repository.