• NOW LIVE! Into the Woods--new character species, eerie monsters, and haunting villains to populate the woodlands of your D&D games.

Klingon Software Design

Mystery Man

First Post
The Klingon Programmer's Code of Honour

All Klingons who develop code for the glory of the empire follow this "Code of Honour" for software "code warriors".

-----

Specifications are for the weak and timid.

State-of-the-art hardware is a prerequisite to do battle with code.

One cannot truly appreciate "Dilbert" without reading it in the original Klingon.

Indentation is for enemy skulls, not code.

Klingons do not "release" software. Klingon software escapes, leaving a bloody trail of design engineers and quality assurance people in its path.

Klingon function calls have no parameters. They have arguments! And they always win them.

Klingons do not debug. Our software does not coddle the weak.

Quality Assurance issues are best solved with a Batleth.

A true Klingon warrior does not comment his code.

Our users shall know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are!
 

log in or register to remove this ad

Mystery Man said:
The Klingon Programmer's Code of Honour

All Klingons who develop code for the glory of the empire follow this "Code of Honour" for software "code warriors".
Hmmm, idea for a D20 Future Advanced Class is now brewing in my mind.
 

Mystery Man said:
Klingons do not "release" software. Klingon software escapes, leaving a bloody trail of design engineers and quality assurance people in its path.

Klingon function calls have no parameters. They have arguments! And they always win them.

Klingons do not debug. Our software does not coddle the weak.

Those are great! :lol:
 

I've known programmers like this.

The worst thing I think I ever saw in a procedure was a function that returned like 36 unique variables (as output from a database query). They were called:

var1, var2, var3, var4 ... var36

I could have shot that guy.
 




Into the Woods

Remove ads

Top