Foundation Stone #25 - Procrastination can be costly
As a developer the focus will be on to quickly complete the task at hand and any developer would wish everything worked perfect the first time. The focus will be to implement the logic that is in mind and the ones that will be left out are things like,
a. Comments/Documentation
b. Essential log information
c. Unit Test code
d. Proper error and exception handling (for example handling the generic Exception in java is not a good practice)
There could be more to the list. But the point here is that it is too tempting for a developer to just make the program work and postpone the above as anyone seeing the output will not know whether the above points were taken care of or not. But the above help in code readability, maintainability and quality of the program and are equally important as the program’s output. Procrastination to the last minute can be costly as even the above could induce human errors and it can lead all the way to a problem in production. The best way to make sure the above points are covered is to have self discipline and follow the standards and best practices in the first place. As a developer when you estimate and give a time line include all the necessary tasks that include the above and any other points so that you don’t need to postpone them to a later time.
