Voip Supply - To find the appropriate contact at InformationWeek, visit our "Contact Us" page, which includes a list of reporters and their beats.

http://www.informationweek.com/contactus.jhtml

And thank you for your interest in InformationWeek.

--

Mitch Wagner | Executive Editor | http://InformationWeek.com | +1 (213) 514-5597 | AIM: mwagner4 | http://www.twitter.com/MitchWagner | mwagner@techweb.com

Voip Supply - To find the appropriate contact at InformationWeek, visit our "Contact Us" page, which includes a list of reporters and their beats.

http://www.informationweek.com/contactus.jhtml

And thank you for your interest in InformationWeek.

--

Mitch Wagner | Executive Editor | http://InformationWeek.com | +1 (213) 514-5597 | AIM: mwagner4 | http://www.twitter.com/MitchWagner | mwagner@techweb.com

Ugh. Well, a day that starts out like that can only get better. :)

This may not be *the* most embarrassing, but it's the one that sticks in my head ... earlier this year, I was trying to fix a bug in a program. I fixed the code, compiled, put the program in place, and tried it. No change in behavior. Tried something else, no change. On and on went the edit/compile/fail cycle, for hours. I went to lunch frustrated, and when I came back I checked where my compile was copying the executable ... and it was to a temporary directory, and not the executable directory. I was running the same program over and over for hours, and the fix was sitting out there the whole time, just in the wrong place. The rest of the day went a little smoother.

What's your most embarrassing technology error? Tell us about a mistake you made where you should've known better.

I sometimes go through heroic efforts to find out why a device has stopped responding. After several hours of work, I'll discover it was because I unplugged it. I do this every year or so.