The importance of version control __hibernate

At the end of 2006, as the original project was about to come online, another project team (the real project team I'm in) is short of staff, so I was transferred to the current project team, the project is a logistics project, levy on different modules, the use of different models, the main part of the use of B/s mode (b/s mode of interaction is relatively poor, But easy to maintain and deploy), the other modules adopt C/S mode (good interactivity, but more complex, technology poured out a lot, like struts,hibernate, even with the weight of the EJB, just into the project team, the person in charge let me do the bill (in fact, the report), let me start from the account ticket, Slowly familiar with the business, I began to feel that should be more relaxed, then I found that there is no version of the management, each assume responsibility for their own module, and so on, and then manually merge, the beginning of the time there is no problem, that version control is not very important, this is also very fast, to later, Since some people have changed some code, program problems, and then to the original code, so that the original merged part of the department will be lost, responsible for this part of the people have to recoding the code, I am the victim, and some of the tickets were covered 3, 4 times, I have to do important to do 3, 4 times, This is not a problem with versioning, and then we find that the problem is serious, plus versioning, and it feels like a lot easier to work with.