|
|
|
| Welcome to the Monastery | |
| PerlMonks |
Re: Re: Are debugging skills atrophying?by mothra (Hermit) |
| on Apr 27, 2001 at 23:10 UTC ( [id://76233]=note: print w/replies, xml ) | Need Help?? |
|
Didn't we do a debugging thread here a while back? Might be worth it to check. You probably meant this one. :) Note that this methodology works for command-line, CGI, and whatever. ...except that it's a little bit more difficult in, for example, GUI programming. ie. It's not always easy to draw up a whole new form to test something out. For smaller, command-line and CGI's it should always be feasible to pull some piece aside though and examine it (I find Python's interactive prompt nice for this too.) Another element is "understand what you type". This does sound so basic, but I still forget this fairly often. :) So maybe the combined rule is "never type faster than you can understand". {grin} Agreed. Quality over speed is most often the right path to take, IMHO. Like the previous point cited though, this too may be oft forgotten.
In Section
Meditations
|
|
||||||||||||||||||||||