The pattern here, as with other hackish grammatical quirks, is generalization of an inflectional rule that in English is either an import or a fossil (such as the Hebrew plural ending `-im', or the Anglo-Saxon plural suffix `-en') to cases where it isn't normally considered to apply.
This is not `poor grammar', as hackers are generally quite well aware of what they are doing when they distort the language. It is grammatical creativity, a form of playfulness. It is done not to impress but to amuse, and never at the expense of clarity.
2.1.5. Spoken Inarticulations
Words such as `mumble', `sigh', and `groan' are spoken in places where their referent might more naturally be used. It has been suggested that this usage derives from the impossibility of representing such noises in electronic mail. Interestingly, the same sorts of constructions have been showing up with increasing frequency in comic strips. Another expression sometimes heard is "Complain!" meaning "I have a complaint!"
2.1.6. Anthropomorphization
Semantically, one rich source of jargon constructions is the hackish tendency to anthropomorphize hardware and software. This isn't done in a naive way; hackers do not believe that the things they work on every day are `alive' but it is common to hear of hardware or software as though it has some creatures talking to each other inside it, with intentions and desires. E.g.: "The protocol handler got confused", «Programs are trying to do smth», «A routine’s goal in life is to X". One even hears explanations like " . and its poor little brain couldn't understand X, and it died."
Anything with a really complex behavioral repertoire is usually thought of as `like a person' rather than `like a thing'. Thus, anthropomorphisation makes sentences easier to understand.
2.1.7. Comparatives
Many words in hacker jargon have to be understood as members of sets of comparatives. This is especially true of the adjectives and nouns used to describe the beauty and functional quality of code. Here is an approximately correct spectrum:
monstrosity
brain-damage
screw
bug
lose
misfeature
crock
kluge
hack
win
feature
elegance
perfection
The last is spoken of as a mythical absolute, approximated but never actually attained.
Another similar scale is used for describing the reliability of software: broken
flaky
dodgy
fragile
brittle
solid
robust
bulletproof
armor-plated
`Dodgy' is primarily Commonwealth Hackish and it is rare in the U.S.A. and may change places with `flaky' for some speakers.
Coinages for describing lossage seem to call forth the very finest in hackish linguistic inventiveness.
It has been truly said that hackers have even more words for equipment failures than Yiddish has for obnoxious people.
2.2. Hacker Style
2.2.1. Hacker Speech Style
Hackish speech generally features extremely precise diction, careful word choice, a relatively large working vocabulary, and relatively little use of contractions or street slang. Dry humor, irony, puns, and a mildly flippant attitude are highly valued -- but an underlying seriousness and intelligence are essential. One should use just enough jargon to communicate precisely and identify oneself as a member of the culture; overuse of jargon or a breathless, excessively gung-ho attitude is not respected.
This speech style is a variety of the precisionist English normally spoken by scientists, design engineers, and academics in technical fields. In contrast with the methods of jargon construction, it is fairly constant throughout hackerdom.
It has been observed that many hackers are confused by negative questions - or the people to whom they talk are often confused by the sense of their answers. They have done so much programming that distinguishes between if (going) . that means «If we are going» and if (!going) .that means «If we are not going» when they parse the question "Aren't you going?" it seems to be asking the opposite question from "Are you going?", and so merits an answer in the opposite sense. This confuses English-speaking non-hackers because they were taught to answer as though the negative part weren't there. In some other languages (including Russian, Chinese, and Japanese) the hackish interpretation is standard and the problem wouldn't arise. Hackers often find themselves wishing for a word like French `si' or German `doch' with which one could unambiguously answer `yes' to a negative question.
For similar reasons, English-speaking hackers almost never use double negatives, even if they live in a region where colloquial usage allows them. The thought of uttering something that logically ought to be an affirmative knowing it will be misparsed as a negative tends to disturb them.
In a related vein, hackers sometimes make a game of answering questions containing logical connectives with a strictly literal rather than colloquial interpretation. A non-hacker who is indelicate enough to ask a question like "So, are you working on finding that bug now or leaving it until later?" is likely to get the perfectly correct answer "Yes!" (that is, "Yes, I'm doing it either now or later, and you didn't ask which!").
2.2.2.Hacker Writing Style
As it has been said, hackers often coin jargon by generalizing grammatical rules. This is one aspect of a more general fondness for form-versus-content language jokes that shows up particularly in hackish writing. Hackers claim that many people have been known to criticize hacker jargon by observing: «This sentence no verb», or «Too repetetetive», or «Bad speling», or «Incorrectspa cing.»
Similarly, intentional spoonerisms are often made of phrases relating to confusion or things that are confusing; `dain bramage’ for `brain damage’ is perhaps the most common (similarly, a hacker would be likely to write «Excuse me, I’m cixelsyd today», rather than «I’m dyslexic today»). This sort of thing is quite common and is enjoyed by all concerned.
Hackers tend to use quotes as balanced delimiters like parentheses, much to the dismay of American editors. Thus, if «Jim is going» is a phrase, and so are «Bill runs» and «Spock groks», then hackers generally prefer to write: «Jim is going», «Bill runs», and «Spock groks». This is incorrect according to Standard American usage (which would put the continuation commas and the final period inside the string quotes).
Hackers tend to distinguish between `scare’ quotes and `speech’ quotes; that is, to use British-style single quotes for marking and reserve American-style double quotes for actual reports of speech or text included from elsewhere. Interestingly, some authorities describe this as correct general usage.
One further not standard permutation is a hackish tendency to do marking quotes by using apostrophes (single quotes) in pairs; that is, ‘like this’.