Top 10 replies by developers when their programs don't work
-
I just got a message from a friend of mine, I'm sorry if it's a repost here. Top 10 replies by developers when their programs don't work: 10. 'That's weird...' 9. 'It's never done that before.' 8. 'It worked yesterday.' 7. 'You must have the wrong version.' 6. 'It works, but it hasn't been tested.' 5. 'Somebody must have changed my code.' 4. 'Did you check for a virus?' 3. 'Where were you when the program blew up?' 2. 'Why do you want to do it that way?' and finally ... 1. 'I thought I fixed that.'
It's a data issue, nothing to do with the program...
turning the other cheek just gets you slapped twice
-
We've just had that with a make system but "my computer" is a Linux box so they don't care that we have Windows. The tigress is here :-D
Trollslayer wrote:
but "my computer" is a Linux box
:eek:
-
I just got a message from a friend of mine, I'm sorry if it's a repost here. Top 10 replies by developers when their programs don't work: 10. 'That's weird...' 9. 'It's never done that before.' 8. 'It worked yesterday.' 7. 'You must have the wrong version.' 6. 'It works, but it hasn't been tested.' 5. 'Somebody must have changed my code.' 4. 'Did you check for a virus?' 3. 'Where were you when the program blew up?' 2. 'Why do you want to do it that way?' and finally ... 1. 'I thought I fixed that.'
-
I just got a message from a friend of mine, I'm sorry if it's a repost here. Top 10 replies by developers when their programs don't work: 10. 'That's weird...' 9. 'It's never done that before.' 8. 'It worked yesterday.' 7. 'You must have the wrong version.' 6. 'It works, but it hasn't been tested.' 5. 'Somebody must have changed my code.' 4. 'Did you check for a virus?' 3. 'Where were you when the program blew up?' 2. 'Why do you want to do it that way?' and finally ... 1. 'I thought I fixed that.'
I've pretty much used them all, and sometimes several in a row. Tye forgot: "hmmm...." Marc VS2005 Tips & Tricks -- contributions welcome!
-
I just got a message from a friend of mine, I'm sorry if it's a repost here. Top 10 replies by developers when their programs don't work: 10. 'That's weird...' 9. 'It's never done that before.' 8. 'It worked yesterday.' 7. 'You must have the wrong version.' 6. 'It works, but it hasn't been tested.' 5. 'Somebody must have changed my code.' 4. 'Did you check for a virus?' 3. 'Where were you when the program blew up?' 2. 'Why do you want to do it that way?' and finally ... 1. 'I thought I fixed that.'
-
minhpc_bk wrote:
and finally ... 1. 'I thought I fixed that.'
0. But it works on my computer! Nish :-D
-
I just got a message from a friend of mine, I'm sorry if it's a repost here. Top 10 replies by developers when their programs don't work: 10. 'That's weird...' 9. 'It's never done that before.' 8. 'It worked yesterday.' 7. 'You must have the wrong version.' 6. 'It works, but it hasn't been tested.' 5. 'Somebody must have changed my code.' 4. 'Did you check for a virus?' 3. 'Where were you when the program blew up?' 2. 'Why do you want to do it that way?' and finally ... 1. 'I thought I fixed that.'
How about: "Have you tried rebooting?" ----------------------------- Try my Batch Image Processing Software
-
How about: "Have you tried rebooting?" ----------------------------- Try my Batch Image Processing Software
BigAndy wrote:
How about: "Have you tried rebooting?"
How about: "Have you tried re-installing Windows?" :laugh:
The two most common elements in the universe are Hydrogen and stupidity. - Harlan Ellison Awasu 2.1.3 [^]: A free RSS reader with support for Code Project.
-
I just got a message from a friend of mine, I'm sorry if it's a repost here. Top 10 replies by developers when their programs don't work: 10. 'That's weird...' 9. 'It's never done that before.' 8. 'It worked yesterday.' 7. 'You must have the wrong version.' 6. 'It works, but it hasn't been tested.' 5. 'Somebody must have changed my code.' 4. 'Did you check for a virus?' 3. 'Where were you when the program blew up?' 2. 'Why do you want to do it that way?' and finally ... 1. 'I thought I fixed that.'
some I have heard.... It will go away with a hardware upgrade That is in a 3rd party DLL not my fault That is hardware, not software It is Microsoft's fault and the #1 I hear But I only changed one line.... I tend to be more of the stunned approach... hmmmm.... it didn't do that before, I don't suppose you can send your setup files and data? I don't blame the data, but I cannot fix something for an unexpected event. Sometimes I can, but not always. I have explained that we should not crash from any data input, good, bad or completely insanely out of this world (can be taken litterally in this context). So I don't excuse bugs, but I do like to get datasets to repeat them and fix them. But I am guilty of the #1 also, big time.... _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
I just got a message from a friend of mine, I'm sorry if it's a repost here. Top 10 replies by developers when their programs don't work: 10. 'That's weird...' 9. 'It's never done that before.' 8. 'It worked yesterday.' 7. 'You must have the wrong version.' 6. 'It works, but it hasn't been tested.' 5. 'Somebody must have changed my code.' 4. 'Did you check for a virus?' 3. 'Where were you when the program blew up?' 2. 'Why do you want to do it that way?' and finally ... 1. 'I thought I fixed that.'
-
I've used 8 of these in house, only exceptions being "other devs fault" (I'm the only person writting code for it), and virus.
fat_boy wrote:
'It is a windows bug, nothing to do with me!'
Never used that one. I found a compiler bug last afternoon/this morning though. I'm still working on distilling it down to something small enough to submit to the MS bug tracker, but in 03 I've found a circumstance where hte compiler will optimize away away an else statement and execute it's code always. I also still need to test under 05, I'll do that this evening.
-
I just got a message from a friend of mine, I'm sorry if it's a repost here. Top 10 replies by developers when their programs don't work: 10. 'That's weird...' 9. 'It's never done that before.' 8. 'It worked yesterday.' 7. 'You must have the wrong version.' 6. 'It works, but it hasn't been tested.' 5. 'Somebody must have changed my code.' 4. 'Did you check for a virus?' 3. 'Where were you when the program blew up?' 2. 'Why do you want to do it that way?' and finally ... 1. 'I thought I fixed that.'
My conversation goes something to the effect of... "That's wierd, it worked yesterday - are you sure you have the latest version? You do? I thought I fixed that in the version I just deployed last night." The other common excuse I use is... "That's a bug in Microsoft Commerce Server" :laugh:
-
I just got a message from a friend of mine, I'm sorry if it's a repost here. Top 10 replies by developers when their programs don't work: 10. 'That's weird...' 9. 'It's never done that before.' 8. 'It worked yesterday.' 7. 'You must have the wrong version.' 6. 'It works, but it hasn't been tested.' 5. 'Somebody must have changed my code.' 4. 'Did you check for a virus?' 3. 'Where were you when the program blew up?' 2. 'Why do you want to do it that way?' and finally ... 1. 'I thought I fixed that.'
:laugh:I have to be honest here. I'm very surprised that "Ahhhhhhh, Sh!t!!!" wasn't in there. In Idaho that one has it's own API and everything.
Some assembly required. Code-frog System Architects, Inc.