{"id":679,"date":"2012-04-19T01:53:36","date_gmt":"2012-04-19T01:53:36","guid":{"rendered":"http:\/\/madprogrammer76.wordpress.com\/?p=679"},"modified":"2012-04-19T01:53:36","modified_gmt":"2012-04-19T01:53:36","slug":"do-i-need-source-control","status":"publish","type":"post","link":"https:\/\/andrewpallant.ca\/wordpress\/do-i-need-source-control\/","title":{"rendered":"Do I Need Source Control"},"content":{"rendered":"

Yes! \u00a0<\/strong>For the first time in my 15-year career I had experienced what it is like to not have source control, and I had hated it. \u00a0I had lost a very difficult to write SQL statement in a project. \u00a0It seemed almost impossible to rewrite the SQL for the second time. \u00a0 I believe it was two of us working in the same project that had caused this loss of code. \u00a0 I take the blame because I am the manager and I knew that source control was not implemented. \u00a0I should have taken the time to take all of the projects and check them into the source control system.<\/p>\n

There are a number of reasons to use source control systems and they include:<\/p>\n

    \n
  1. More than one person can work on the same file and then merge the versions together as one file.<\/li>\n
  2. Track changes to a build.<\/li>\n
  3. Control what changes or features is included in a build.<\/li>\n
  4. Safe guard against accidental code loss.<\/li>\n
  5. Track coding efforts by developers<\/li>\n<\/ol>\n

    Types of Source Control – I have used each<\/strong><\/p>\n