Top 12 Things A Klingon Programmer Would Say<\/p>\n
12. Specifications are for the weak and timid!<\/p>\n
11. This machine is a piece of GAGH! I need dual processors if I am to do battle with this code!<\/p>\n
10. You cannot really appreciate Dilbert unless you’ve read it in the original Klingon.<\/p>\n
9. Indentation?! — I will show you how to indent when I indent your skull!<\/p>\n
8. 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.<\/p>\n
7. Klingon function calls do not have ‘parameters’ — they have ‘arguments’ — and they ALWAYS WIN THEM.<\/p>\n
6. Debugging? Klingons do not debug. Our software does not coddle the weak.<\/p>\n
5. I have challenged the entire quality assurance team to a Bat-Leth contest. They will not concern us again.<\/p>\n
4. A TRUE Klingon Warrior does not comment his code!<\/p>\n
3. By filing this SCR you have challenged the honor of my family. Prepare to die!<\/p>\n
2. You question the worthiness of my code? I should kill you where you stand!<\/p>\n
1. Our users will know fear and cower before our software. Ship it! Ship it, and let them flee like the dogs they are!<\/p>\n
Seeing as how old school programmers think like klingon programmers, I believe that it can be reasonably assumed that all old programmers are klingon.<\/p>\n","protected":false},"excerpt":{"rendered":"
Top 12 Things A Klingon Programmer Would Say 12. Specifications are for the weak and timid! 11. This machine is a piece of GAGH! I need dual processors if I am to do battle with this code! 10. You cannot…<\/span><\/p>\n