Boards
Programmer's Speak
Not seen this before...doesn't mean it's not 2 decades old and started way back on the ARPANET, though...
I do know everything, just not all at once. It's a virtual memory problem.
Code so clean you could eat off it!
A computer scientist is someone who, when told to 'Go to Hell', sees the 'go to', rather than the destination, as harmful.
A core dump is your computer's way of saying "Here's what's on my mind, what's on yours?"
A good programmer is someone who looks both ways before crossing a one-way street.
Calculating in binary code is as easy as 01,10,11.
Computer Science: solving today's problems tomorrow.
Documentation is like sex: when it is good, it is very, very good. And when it is bad, it is still better than nothing.
Hey! It compiles! Ship it!
My operat~1 system unders~1 long filena~1 , does yours?
Programmer's Drinking Song: 99 programming bugs in the code / 99 programing bugs / Fix one bug / compile it again / now there's 100 bugs in the code!
Real programmers don't document. If it was hard to write, it should be hard to understand.
Software isn't released, it's allowed to escape.
There are 10 kinds of people in the world: Those who understand binary and those who don't...
To understand recursion, first you've got to understand recursion.
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."
I do know everything, just not all at once. It's a virtual memory problem.
Code so clean you could eat off it!
A computer scientist is someone who, when told to 'Go to Hell', sees the 'go to', rather than the destination, as harmful.
A core dump is your computer's way of saying "Here's what's on my mind, what's on yours?"
A good programmer is someone who looks both ways before crossing a one-way street.
Calculating in binary code is as easy as 01,10,11.
Computer Science: solving today's problems tomorrow.
Documentation is like sex: when it is good, it is very, very good. And when it is bad, it is still better than nothing.
Hey! It compiles! Ship it!
My operat~1 system unders~1 long filena~1 , does yours?
Programmer's Drinking Song: 99 programming bugs in the code / 99 programing bugs / Fix one bug / compile it again / now there's 100 bugs in the code!
Real programmers don't document. If it was hard to write, it should be hard to understand.
Software isn't released, it's allowed to escape.
There are 10 kinds of people in the world: Those who understand binary and those who don't...
To understand recursion, first you've got to understand recursion.
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."