I don't think I've experienced this one yet. Probably the closest was when we converted VB6 modules to C#. It was a GUI application and I converted the controls one by one, including the position, color, etc. It took me almost a week to convert it. Turns out Visual Studio can convert it to VB.Net and my coworker is already doing that. I should have asked.
+6
A:
getting caught answering silly questions on stackOverflow instead of programming....
csmba
2008-08-20 06:24:47
+1
A:
Most of my bad programming moments are frustration from things not working, not really embarrassing. The closest thing to that was I was making a program @ work to work with registry settings. I exported some settings to test on the PC @ my desk, but didn't realize that I had exported EVERY setting from the copy instead of just one small tree of keys. I totally hosed my system for something that was supposed to be simple reading and writing. It took me at least a couple of days to get my system back the way it was. I ended up using a db instead and vowed I would do as little as possible with registry settings in the future :D
Jason Shoulders
2008-08-20 06:25:19
A:
It's not really programming, but in my first IT job I did a kldload snddriver in what i thought was a terminal on my desktop machine. It turned out to be the mailserver and it crashed hard!
svrist
2008-08-20 06:25:54
+5
A:
I had just joined Digital Switch, and was the alleged super-guru of some particular technology. One of my first assignments was to give a seminar on that topic to the group, about 20-some people.
I walked to the table in the front of the room, introduced myself, took a drink to prepare to speak, choked, and spewed an entire mouthful of water all over the table, my notes, everything.
Oh well, there was no place to go but up.
Mark Harrison
2008-08-20 06:38:55
+1
A:
Just yesterday. Wrote some code to have the extension removed from a file path complete with a while loop over the chars in the string... while being pointed by a colleague to the wonderful methods in the Path namespace, e.g. Path.GetFileNameWithoutExtension :) that could have helped me out
Which goes to show that you have to keep thinking before coding...
OK, to be honest, this is not the most embarrassing moment ever, no one would believe me if I said so...
ArjanZuidhof
2008-08-20 06:56:56
+8
A:
For me its when women mock the size of my code.. I keep trying to tell them its quality, not quantity.. But they don't listen, they just point and laugh.. :(
:D
Rob Cooper
2008-08-20 07:03:58
+1
A:
I was once going over the mysql database we were using on a project, to prepare it for putting it in production later that day. I was using PhpMyAdmin, and we had a few tables that were no longer in use, so I thought I'd "DROP" them. DROP'ing table after table, at one point I hit the wrong drop button by mistake, and dropped the whole database. Lets just say we didn't make it into production that day...
Erlend Halvorsen
2008-08-20 08:56:55