|
The source code version control seems to be quite common in large organizations. Therefore, the tip is of small and medium enterprises, in which the source is not under version control oriented. The developers of many small businesses, I think, working versions of the source code unnecessary surgery. Ironically, many of these small companies start sites require high availability to be economically viable. The importance of the source code control in high-availability version 24 * 7 working hours and cannot be overstated. Imagine a situation this way: We just published a mission critical application. Six of the organizers involved in writing code. Each programmer has written several programs. Each developer has the source code in the list. After a few weeks, end users must request changes and several programs to modify to adapt to new needs. The developer who worked hard, is absent from work. In contrast, another developer made a copy of the source code, make changes and put into use, after appropriate testing. Even after a couple of weeks, users demand more than a few additions to the programs. But now, the original developer is working in these work programs. I just heard today about the new requirements, the old source code quickly moved to a local directory, any changes it deems appropriate subject, and pushes it to production. Working quickly, of course, was too fast. Well, in this case only describes the changes made by other developers missing the original developers lost. Application version will always be displayed due to changes and errors to another developer to explain. However, if the code is old, so there's no trick available to determine what the latest version. In the list, we can apply all these errors and changes for each application. Unfortunately, in the most cases, this type of document is or not the rate of retention. If you are experiencing is not properly updated by the change. One reason may be to change the work of programmers, long vacation, temporary developers move to outsourcing, etc. The source code version control is avoided because the scenarios, where multiple copies and versions in circulation, which can be considerable confusion and downtime, as valuable time, which is designed to identify and correct errors. Million scenarios as above come to mind. In short, the moral of the story is this - in order to ensure that all the source code of the production version will be controlled, and all versions are directed by the correct order, without criticism from others. Version control allows you to receive a contingency plan prior to the introduction of any new code. If the new code has serious errors, the fund will set aside and return to the previous version of the program or application. Gitesh Trivedi has 14+ years of experience and author of technical writing of Remote Oracle Support and also author of Oracle DBA Interview Questions with answers books.
Related Articles -
version control, source code version control, version control system, software version control, it development, version management,
|
