Verification Jokes

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

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

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

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

Report submitted by banta singh to his manager after completing his y2k
Verification task. dear sir,
Our staff has completed the 18 months of work on time and on
Budget. We have gone through every line of code
In every program in every system. We have analyzed all databases, all data
Files, including backups and historic
Archives, and modified all data to reflect the change. We are proud to
Report that we have completed the "y-to-k"
Date change mission, and have now implemented all changes to all programs
And all data to reflect your new standards:
Januark, februark, march, april, mak, june, julk,
August, september, october, november, december
As well as:
Sundak, mondak, tuesdak, wednesdak thursdak, fridak, saturdak.
I trust that this is satisfactory, because to be honest, none of
This y to k problem has made any sense to
Me. But i understand it is a global problem, and our team is glad to more...