Salesforce without version control:
Imagine a world without version control. Scary right? But that’s how it has been for salesforce since the beginning. For those who have never worked with a version control system and are wondering what the hell is it, think of it as a safe deposit box for your code with an ability to travel in the past. For more details visit Getting Started About Version Control. So, going back, Salesforce didn’t have a way to track changes or maintain a version control to begin with. One might ask the question why? It is pretty obvious, isn’t it? Salesforce started primarily as a CRM tool where the most changes you would do were just configuration changes. A little drag and drop here and there and you are ready. Change sets were good enough back then. Maintaining changes wasn’t that difficult.
Customisations!! Soon the customers started to realise the customisation potential of salesforce. They started coming up with requirements which could no longer be delivered with just drag and drop or simple configurations.
In the beginning it was just a little bit but eventually the amount of coding implementations started increasing. To the point where multiple developers needed to work on the same file. You know where I am going with this. Everyone started realising the need for a VCS.