I think that this page is not explaining the techniques well. The page does not contain any examples or a step-by-step guide, but rather is written in plain text. Beginners, for whom this article is intended, will not know exactly how to process without any experience before.
There should be steps which will explain the debugging method which is appropriate in that case (using goto for syntax errors, checking the variable's value at time of crash, get a printed version of the program and match the Then and Ends with tabs, use the Pause command to continuously check the value of a variable and finally (or often before) ask in the forum for help).
The example could be some screenshots of the calks with 6 lines of code and an error showing how to solve the bugs. Generally, it is important to distinct bugs (syntax errors, missing ends) from logical errors (variable has got faulty value, Memory leak, missing "declaration of variables") because the logical errors can be solved by the community rather then the bugs.
Then in the end there should be a "Advices" section with rather unimportant advices like don't blame the calc, take a nap, write ends directly when writing thens,… so that the important content is not blurred by these rather unimportant things.
Finally, there are some points I don't agree with. For example, I don't understand why somebody should delete code of the program to find the bug. I would rather suggest especially for more complex programs to try (almost) all different ways of using the program and using Pause A or whatever variable to check variables and slowly find the logical error.
Get futuristicOS 8 for your TI-84+
Learn more about futuristicOS 8