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."

20. 거 이상하네요
19. 전에는 이런적 없는데
18. 어젠 됬는데
17. 어떻게 그럴수 있죠?
16. 분명히 하드웨어 문제일겁니다
15. 뭘 잘못 입력했길래 다운시킨거에요?
14. 데이터에 뭔가 문제가 있네요.
13. 그 모듈은 안 건드린지 몇주나 되었는데요
12. 최신버전 까셨나요?
11. 안좋은 우연이네요.
10. 짠거 다 테스트는 할수없잖아;?
9. 그 소스로는 이럴리가 없는데
8. 만들긴했는데 테스트는 안해봤어요
7. 누가 내 코드를 바꿨어요
6. 당신자리 바이러스 검사해보셍
5. 동작하진 않았지만, 느낌이 어때요?
4. 당신컴에서는 그버전 못써요
3. 왜 이방식으로 하려고 만하죠?
2. 이지경이 될대까지 뭐하고있었냐
1. 제자리선 잘되는데요

 

 

1번은 무적의 치트입니다. poweroverwhelming.