real software engineers
Real software engineers eat quiche.
Real software engineers don't read dumps. They never generate them, and on the rare occasions that they come across them, they are vaguely amused.
Real software engineers don't comment their code. The identifiers are so mnemonic they don't have to.
Real software engineers don't write applications programs, they implement algorithms. If someone has an application that the algorithm might help with, that's nice. Don't ask them to write the user interface, though.
If it doesn't have recursive function calls, real software engineers don't program in it.
Real software engineers don't program in assembler. They become queasy at the very thought.
Real software engineers don't debug programs, they verify correctness. This process doesn't necessarily involve executing anything on a computer, except perhaps a Correctness Verification Aid package.
Real software engineers like C's structured constructs, but they are suspicious of it because they have heard that it lets you get "close to the machine."
Real software engineers play tennis. In general, they don't like any sport that involves getting hot and sweaty and gross when out of range of a shower. (Thus mountain climbing is Right Out.) They will occasionally wear their tennis togs to work, but only on very sunny days.
Real software engineers admire PASCAL for its discipline and Spartan purity, but they find it difficult to actually program in. They don't tell this to their friends, because they are afraid it means that they are somehow Unworthy.
Real software engineers work from 9 to 5, because that is the way the job is described in the formal spec. Working late would feel like using an undocumented external procedure.
Real software engineers write in languages that have not actually been implemented for any machine, and for which only the formal spec (in BNF) is available. This keeps them from having to take any machine dependencies into account. Machine dependencies make real software engineers very uneasy.
Real software engineers don't write in ADA, because the standards bodies have not quite decided on a formal spec yet.
Real software engineers like writing their own compilers, preferably in PROLOG (they also like writing them in unimplemented languages, but it turns out to be difficult to actually RUN these).
Real software engineers regret the existence of COBOL, FORTRAN and BASIC. PL/I is getting there, but it is not nearly disciplined enough; far too much built in function.
Real software engineers aren't too happy about the existence of users, either. Users always seem to have the wrong idea about what the implementation and verification of algorithms is all about.
Real software engineers don't like the idea of some inexplicable and greasy hardware several aisles away that may stop working at any moment. They have a great distrust of hardware people, and wish that systems could be virtual at ALL levels. They would like personal computers (you know no one's going to trip over something and kill your DFA in mid-transit), except that they need 8 megabytes to run their Correctness Verification Aid packages.
Real software engineers think better while playing WFF 'N' PROOF.
Real software engineers don't read dumps. They never generate them, and on the rare occasions that they come across them, they are vaguely amused.
Real software engineers don't comment their code. The identifiers are so mnemonic they don't have to.
Real software engineers don't write applications programs, they implement algorithms. If someone has an application that the algorithm might help with, that's nice. Don't ask them to write the user interface, though.
If it doesn't have recursive function calls, real software engineers don't program in it.
Real software engineers don't program in assembler. They become queasy at the very thought.
Real software engineers don't debug programs, they verify correctness. This process doesn't necessarily involve executing anything on a computer, except perhaps a Correctness Verification Aid package.
Real software engineers like C's structured constructs, but they are suspicious of it because they have heard that it lets you get "close to the machine."
Real software engineers play tennis. In general, they don't like any sport that involves getting hot and sweaty and gross when out of range of a shower. (Thus mountain climbing is Right Out.) They will occasionally wear their tennis togs to work, but only on very sunny days.
Real software engineers admire PASCAL for its discipline and Spartan purity, but they find it difficult to actually program in. They don't tell this to their friends, because they are afraid it means that they are somehow Unworthy.
Real software engineers work from 9 to 5, because that is the way the job is described in the formal spec. Working late would feel like using an undocumented external procedure.
Real software engineers write in languages that have not actually been implemented for any machine, and for which only the formal spec (in BNF) is available. This keeps them from having to take any machine dependencies into account. Machine dependencies make real software engineers very uneasy.
Real software engineers don't write in ADA, because the standards bodies have not quite decided on a formal spec yet.
Real software engineers like writing their own compilers, preferably in PROLOG (they also like writing them in unimplemented languages, but it turns out to be difficult to actually RUN these).
Real software engineers regret the existence of COBOL, FORTRAN and BASIC. PL/I is getting there, but it is not nearly disciplined enough; far too much built in function.
Real software engineers aren't too happy about the existence of users, either. Users always seem to have the wrong idea about what the implementation and verification of algorithms is all about.
Real software engineers don't like the idea of some inexplicable and greasy hardware several aisles away that may stop working at any moment. They have a great distrust of hardware people, and wish that systems could be virtual at ALL levels. They would like personal computers (you know no one's going to trip over something and kill your DFA in mid-transit), except that they need 8 megabytes to run their Correctness Verification Aid packages.
Real software engineers think better while playing WFF 'N' PROOF.
signs your computer is bad
10. Lower corner of screen has the words "Etch-a-sketch" on it.
9. It's celebrity spokesman is that "Hey Vern!" guy.
8. In order to start it, you need some jumper cables and a friend's car.
7. It's slogan is "Pentium: redefining mathematics".
6. The "quick reference" manual is 120 pages long.
5. Whenever you turn it on, all the dogs in your neighborhood start howling.
4. The screen often displays the message, "Ain't it break time yet?"
3. The manual contains only one sentence: "Good Luck!"
2. The only chip inside is a Dorito.
1. You've decided that your computer is an excellent addition to your fabulous paperweight collection.
9. It's celebrity spokesman is that "Hey Vern!" guy.
8. In order to start it, you need some jumper cables and a friend's car.
7. It's slogan is "Pentium: redefining mathematics".
6. The "quick reference" manual is 120 pages long.
5. Whenever you turn it on, all the dogs in your neighborhood start howling.
4. The screen often displays the message, "Ain't it break time yet?"
3. The manual contains only one sentence: "Good Luck!"
2. The only chip inside is a Dorito.
1. You've decided that your computer is an excellent addition to your fabulous paperweight collection.
software development
1. Programmer produces code he believes is bug-free.
2. Product is tested. 20 bugs are found.
3. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs.
4. Testing department finds that five of the fixes didn't work and discovers 15 new bugs.
5. Repeat three times steps 3 and 4.
6. Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
7. Users find 137 new bugs.
8. Original programmer, having cashed his royalty check, is nowhere to be found.
9. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
10. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
11. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
12. New CEO is brought in by board of directors. He hires a programmer to redo program from scratch.
13. Programmer produces code he believes is bug-free.
2. Product is tested. 20 bugs are found.
3. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs.
4. Testing department finds that five of the fixes didn't work and discovers 15 new bugs.
5. Repeat three times steps 3 and 4.
6. Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
7. Users find 137 new bugs.
8. Original programmer, having cashed his royalty check, is nowhere to be found.
9. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
10. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
11. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
12. New CEO is brought in by board of directors. He hires a programmer to redo program from scratch.
13. Programmer produces code he believes is bug-free.
some bumper stickers
1. BREAKFAST.COM Halted...Cereal Port Not Responding
2. <-------- The information went data way
3. The name is Baud...James Baud.
4. BUFFERS=20 FILES=15 2nd down, 4th quarter, 5 yards to go!
5. Access denied--nah nah na nah nah!
6. C:V> Bad command or file name! Go stand in the corner.
7. Southern DOS: Y'all reckon? (Yep/Nope)
8. Backups? We don' *NEED* no steenking backups.
9. E Pluribus Modem
10. .... File not found. Should I fake it? (Y/N)
11. Ethernet (n): something used to catch the etherbunny
12. CONGRESS.SYS Corrupted: Re-boot Washington D.C (Y/N)?
13. 11th commandment - Covet not thy neighbor's Pentium.
14. Windows: Just another pane in the glass.
15. SENILE.COM found . . . Out Of Memory . . .
16. RAM disk is *not* an installation procedure.
17. Smash forehead on keyboard to continue...
18. COFFEE.EXE Missing - Insert Cup and Press Any Key
19. ASCII stupid question, get a stupid ANSI!
20. E-mail returned to sender -- insufficient voltage.
21. Error: Keyboard not attached. Press F1 to continue.
22. "640K ought to be enough for anybody." - Bill Gates, 1981
23. Press any key... no, no, no, NOT THAT ONE!
24. Press any key to continue or any other key to quit...
25. REALITY.SYS corrupted: Reboot universe? (Y/N/Q)
26. Error reading FAT record: Try the SKINNY one? (Y/N)
27. Hit any user to continue.
28. Disk Full - Press F1 to belch.
29. Backup not found: (A)bort (R)etry (P)anic
30. (A)bort, (R)etry, (G)et a beer?
2. <-------- The information went data way
3. The name is Baud...James Baud.
4. BUFFERS=20 FILES=15 2nd down, 4th quarter, 5 yards to go!
5. Access denied--nah nah na nah nah!
6. C:V> Bad command or file name! Go stand in the corner.
7. Southern DOS: Y'all reckon? (Yep/Nope)
8. Backups? We don' *NEED* no steenking backups.
9. E Pluribus Modem
10. .... File not found. Should I fake it? (Y/N)
11. Ethernet (n): something used to catch the etherbunny
12. CONGRESS.SYS Corrupted: Re-boot Washington D.C (Y/N)?
13. 11th commandment - Covet not thy neighbor's Pentium.
14. Windows: Just another pane in the glass.
15. SENILE.COM found . . . Out Of Memory . . .
16. RAM disk is *not* an installation procedure.
17. Smash forehead on keyboard to continue...
18. COFFEE.EXE Missing - Insert Cup and Press Any Key
19. ASCII stupid question, get a stupid ANSI!
20. E-mail returned to sender -- insufficient voltage.
21. Error: Keyboard not attached. Press F1 to continue.
22. "640K ought to be enough for anybody." - Bill Gates, 1981
23. Press any key... no, no, no, NOT THAT ONE!
24. Press any key to continue or any other key to quit...
25. REALITY.SYS corrupted: Reboot universe? (Y/N/Q)
26. Error reading FAT record: Try the SKINNY one? (Y/N)
27. Hit any user to continue.
28. Disk Full - Press F1 to belch.
29. Backup not found: (A)bort (R)etry (P)anic
30. (A)bort, (R)etry, (G)et a beer?
Page 15 of 20 «« Previous | Next »»