The joy of computer programming

[dr_tectonic]

Memo to myself:

If you're waiting to implement a particular snippet of code until you can figure out why the program is behaving oddly, make sure to consider the possibility that it's behaving oddly because you didn't implement the damn snippet of code yet!

*facepalm*

Comments

An obvious corrolary to the first rule of tech support . . . .

[goobermunch.livejournal.com]

Always make sure the computer is plugged in before examining more drastic measures.

--G

Re: An obvious corrolary to the first rule of tech support . . . .

[detailbear.livejournal.com]

In our office, the rules of tech support:

1. Check the Hardware, Stupid!

2. Never believe what the client says.

3. The more you document a problem, the less likely it is to recur.

Gaak.

[madbodger.livejournal.com]

Been there. My most recent one was where some debugging code appeared to fix the problem. Made no sense whatsoever. Finally I realized that there were several records in the output, and the extra debugging stuff pushed the one that broke off the bottom of my screen.

*facepalm*

Re: Gaak.

[dr-tectonic.livejournal.com]

What I really hate is when you're debugging a problem and you know that it's something stupid and obvious that you just aren't seeing because you're reading what you meant to write and not what you actually wrote.

That's when another pair of eyes is handy.

[madbodger.livejournal.com]

Often, any pair of eyes will do. In fact, just bringing in another person to look at something will sometimes enable me to see the error I couldn't before.