Debugging The Code and Correcting Errors
Programmers usually tend to write the complete code and then begin debugging and checking for errors. Though this approach can save time in smaller projects, bigger and complex ones tend to have too many variables and functions that need attention. Therefore, it is good to debug every module once you are done and not the entire program. This saves time in the long run so that one does not end up wasting a lot of time on figuring out what is wrong.
Read more about this topic: Best Coding Practices
Famous quotes containing the words code, correcting and/or errors:
“...I had grown up in a world that was dominated by immature age. Not by vigorous immaturity, but by immaturity that was old and tired and prudent, that loved ritual and rubric, and was utterly wanting in curiosity about the new and the strange. Its era has passed away, and the world it made has crumbled around us. Its finest creation, a code of manners, has been ridiculed and discarded.”
—Ellen Glasgow (1873–1945)
“I should have no objection to go over the same life from its beginning to the end: requesting only the advantage authors have, of correcting in a second edition the faults of the first.”
—Benjamin Franklin (1706–1790)
“Generally speaking, the errors in religion are dangerous; those in philosophy only ridiculous.”
—David Hume (1711–1776)