This is something I always knew, the text I just find it now. My own understanding at the moment ...
When you make a program and passes to the debugging phase, has not decided before or after running what is wrong, correct it and after verifying that you still can not blame this on the inability of the program to implement the correction. What you do is see where the matter, what lines are running and what not depending on the time, what value the variables take in every moment, and so on. In short, what is observedmakes the program at all times during operation to locate what is bad, without drawing conclusions before finding the error. This concept seemingly simple and reasonable, is stripped of all value for most people when the program is to arrange your own mind. Observation ruled in favor of reasoning. Reason "it is for this and this and that" before or after running the error process, never over, without stopping to look at even what they are modeled.
long time ago that I understood intellectually the logic of this, but one thing to say, "Yes, it makes sense," and another to see for yourself, internalize, or realize the
need to do so. This just happened to mea few days. The result is that for a significant part of the day observed. It is a deliberate act, deliberate, but just the same way it judges the previous thought, calling it good or bad, logical or illogical, consistent or inconsistent spontaneously or automatically, with the same spontaneity is given one realizes the futility and void and passes this observation. Not a question of voluntarily repeat until it becomes a reflex, is something that comes from understanding. Still, I do all the time, I realize my mistakes post (but not its cause, this can only be done at the time). No point in forcing yourself to look more proportion of time day or throughout the day, your