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:
“Faultless honesty is a sine qua non of business life. Not alone the honesty according to the moral code and the Bible. When I speak of honesty I refer to the small, hidden, evasive meannesses of our natures. I speak of the honesty of ourselves to ourselves.”
—Alice Foote MacDougall (1867–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)
“When a Man is in a serious Mood, and ponders upon his own Make, with a Retrospect to the Actions of his Life, and the many fatal Miscarriages in it, which he owes to ungoverned Passions, he is then apt to say to himself, That Experience has guarded him against such Errors for the future: But Nature often recurs in Spite of his best Resolutions, and it is to the very End of our Days a Struggle between our Reason and our Temper, which shall have the Empire over us.”
—Richard Steele (1672–1729)