The idea that once our code is working, we are good to go is a very bad idea. An idea that needs to be reevaluated and analyzed. When you buy a car, it works at first, and then it begins to develop faults. Do you have to wait for the car to develop faults before you begin maintaining it? Well, the answer is obvious and the answer is NO.
But why then do we have to do the same thing to our code. Once a piece of code works or passes that test, we close that code and never ever look back. Even the car at Toyota passed the test before it was delivered to the client, but it also has to be maintained. Some people would argue that code maintenance is far more different from maintaining a car, but I would beg to differ. What is maintained in whatever form is better than what is never maintained?
Continue reading “Code Maintenance”