Re-read the klingon software development guide
I have left the more important points, special attention to: 14, 18 and 19
3. I have challenged the entire ISO-9000 review team to a round of Bat-Leth practice on the holodeck. They will not concern us again.
5. Defensive programming? Never! Klingon programs are always offensive. Yes, offensive programming is what we do best.
6. Klingon programs don't do accountancy. For that, you need a Ferengi programmer.
7. Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM.
9. By filing this bug you have questioned my family honour. Prepare to die!
10. I am without honour...my children are without honour... My father coded at the Battle of Kittimer...and...and...he... HE ALLOWED HIMSELF TO BE MICROMANAGED. <Shudder>
11. You question the worthiness of my code?! I should kill you where you stand!
13. Specs are for the weak and timid!
14. Klingons do not believe in indentation - except perhaps in the skulls of their project managers.
16. Klingons do not "release" software. Klingon software escapes, leaving a bloody trail of design engineers and quality assurance testers in its wake.
17. Debugging? Klingons do not debug. Bugs are good for building up character in the user!
18. As for project orders (requirements, goals): Klingons do not deliver; we EXECUTE. For the glory of the empire!
19. Perhaps it IS a good day to die! I say we ship it!
And the result is:
Qapla [also Kapla from the Klingon language: meaning "success" (or sometimes "absence of failure")]