Version Control and Test Driven Development
Software development is usually quite a task that you need to keep track of every little change you make to your lines of code, files, folders, images, directories e.t.c. We could do this the old way — having newer documents in different folders — which is not only tiresome but also we risk losing a folder or a file by mistakenly deleting them. But don’t worry folks, the good news is that we are no longer in the stone age!
Now we have VERSION CONTROL software that can do more than just keep track of the changes made anywhere in your project. An example of these is Git.
Version control software helps to keep track of changes made anywhere in the project, one can work on a project without affecting the original project files (branching), a team can contribute to one project at the same time without affecting anybody’s work in the team, any changes made anywhere in the project are documented and there’s no fear of losing work as a result of hardware failures since the system is distributed.
With version control, project management can easily be implemented since any alterations on the project are well documented. This is a technique that I have learned and I will implement any day, anywhere, working on any project.
Test driven development, on the other hand, is a technique that many software developers would want to run away from, to be honest, I was also afraid with the phrase itself. But later I understood that its better to teach a cub, than wait until it is a full grown lion! Building software while testing at the same time is a technique that allows us to move forward without looking back, or rather, just move forward.
It involves testing of our outputs, logic, functions, objects…the list is long. It allows moving to a next stage only after stamping the previous one and this is what I call progress.
When these two software engineering techniques are combined, be assured that you can only get good software.