|The stupid question is the question not asked|
Re: Tricking Our Egosby jynx (Priest)
|on Feb 16, 2001 at 02:47 UTC||Need Help??|
Thinking about it, i suppose that is a proper way to explain what is happening for a lot of programmers when they debug. Don't know if i qualify as a programmer but i usually try something like the following:
1) make every block of code simple and direct
2) when debugging, find the blocks of code that relate to the problem
3) Pat yourself on the back for the blocks of code that didn't cause a problem.
4) Triple check that your solution worked
5) Look for the next bug
Me thinks my main problem is that i will always assume there are unsolved bugs in my code, even when it's fully working, even if it's only one line. So patting myself on the back is a way to get myself to continue since i'll know that at least one piece of code is ok.
to each their own, TIMTOWTDI