The Top 20 replies by programmers when it breaks

Monkey Archive Forums/Digital Discussion/The Top 20 replies by programmers when it breaks

AdamRedwoods(Posted 2013) [#1]
The Top 20 replies by programmers when their programs do not work:

20. "That's weird..."
19. "It's never done that before."
18. "It worked yesterday."
17. "How is that possible?"
16. "It must be a hardware problem."
15. "What did you type in wrong to get it to crash?"
14. "There is something funky in your data."
13. "I haven't touched that module in weeks!"
12. "You must have the wrong version."
11. "It's just some unlucky coincidence."
10. "I can't test everything!"
9. "THIS can't be the source of THAT."
8. "It works, but it hasn't been tested."
7. "Somebody must have changed my code."
6. "Did you check for a virus on your system?"
5. "Even though it doesn't work, how does it feel?
4. "You can't use that version on your system."
3. "Why do you want to do it that way?"
2. "Where were you when the program blew up?"

And the Number One reply by programmers when their programs don't work:

1. "It works on my machine."


therevills(Posted 2013) [#2]
LOL! I've said a few of those in my time ;)

"That's weird..."

"It worked yesterday."

"Somebody must have changed mythe code."

"It works on my machine."


dopeyrulz(Posted 2013) [#3]
Hahaha! Yeah heard and used a few of those!


slenkar(Posted 2013) [#4]
'did you delete your build folder?'


ziggy(Posted 2013) [#5]
'did you delete your build folder?'
That one was the best! hehehe


therevills(Posted 2013) [#6]
Maybe Ted/Jungle should ask the user "Do you want to delete your build folder?" every time we compile!!


Neuro(Posted 2013) [#7]
I've used the following just last week at my work :

18. "It worked yesterday."
15. "What did you type in wrong to get it to crash?"
3. "Why do you want to do it that way?"
1. "It works on my machine."

And ironically, i've never actually said this but it usually ends up being the reason why these issues occur :

7. "Somebody must have changed my code."

Go figure :).


Paul - Taiphoz(Posted 2013) [#8]
I cant beleive that this is not on the list.

21. Its not a bug its a new feature.

as for comments Iv made myself , lol probably half the list but mostly when I talk to my main beta tester its something like "that's not finished yet" which is my catch all for saying , crap that's a bug but im not telling him its a bug.


EdzUp(Posted 2013) [#9]
Weirdly us coders must have a magic touch when I worked at a computer shop in Brighton I built several computers where customers said they didn't work for them, so when I went onsite turned on the computer it worked perfectly. Confusingly enough when I got back we got a call saying it didn't work for them again so they brought it back to us, I built them another computer that works fine. We never got to the bottom of the other one as the machine worked fine right up till the shop closed.

Also my step daughter was putting the sims 2 on her computer and was entering the codes to install but a particular code didn't work her mum checked it, her sister checked it perfect but it refused to work. I had a look and it worked first time Lol

Anyone else had those sort of strange experiences with technology?


Neuro(Posted 2013) [#10]
Anyone else had those sort of strange experiences with technology?

All the time :). In my apartment complex, the older folks living there often call on me for computer assistance and for some odd reason anytime i touch it or attempt to reproduce the problem, it just "magically" works again all of sudden. Never can really explain why.