Top 12 Things A Klingon Programmer Would Say

This entry was published at least two years ago (originally posted on May 18, 2005). Since that time the information may have become outdated or my beliefs may have changed (in general, assume a more open and liberal current viewpoint). A fuller disclaimer is available.
  1. Specifications are for the weak and timid!
  2. This machine is a piece of GAGH! I need dual processors if I am to do battle with this code!
  3. You cannot really appreciate Dilbert unless you’ve read it in the original Klingon.
  4. Indentation?! — I will show you how to indent when I indent your skull!
  5. What is this talk of ‘release’? Klingons do not make software ‘releases’. Our software ‘escapes’ leaving a bloody trail of designers and quality assurance people in its wake.
  6. Klingon function calls do not have ‘parameters’ — they have ‘arguments’ — and they ALWAYS WIN THEM.
  7. Debugging? Klingons do not debug. Our software does not coddle the weak.
  8. I have challenged the entire quality assurance team to a Bat-Leth contest. They will not concern us again.
  9. A TRUE Klingon Warrior does not comment his code!
  10. By filing this SCR you have challenged the honor of my family. Prepare to die!
  11. You question the worthiness of my code? I should kill you where you stand!
  12. Our users will know fear and cower before our software. Ship it! Ship it, and let them flee like the dogs they are!

Seeing as how old school programmers think like Klingon programmers, I believe that it can be reasonably assumed that all old programmers are Klingon.

(Found on /.)