Or, failing that, perhaps they used something before it had a name which made it popular. See also: design patterns and anyone who predates their popularity.
If the OP is interested in portraying "hackers" who aren't highly skilled, having them misuse terminology would be a good approach, for example portraying a later mastermind in his early, naive days. But portraying a world-class expert who uses hacker slang but can't get the technical terminology right would be a classic Hollywood error.
The language is an important component of functioning effectively in the domain. And it serves as a thinking aid, as well; it's very difficult to manipulate complex fields without the use of abstractions. Language is part and parcel of those abstractions.
I am in agreement with SiVal. Accurate communication is a clear measure.
Perhaps somewhat akin with the current "brogramming" fettish, one... "Hollywoodism" is to apply some sort of slangy techspeak "bravado" to "elite hackers".
That's B.S.
P.S. I should add that "taught himself" means a combination of reading, doing, and collaborating with others in his fields of interest.
He might have entered some of those fields kind of sideways, but once people within them observed and learned that he really knows what he is doing and what he is talking about, that doesn't matter. (And that he quickly and thoroughly learns things he doesn't already know, when needed. Or... as often as not, before "needed", because of his driving interest.)
to the person who uses: LAMP servers, python script,ubuntu machines, etc. these items are matter of fact tools for what they do and are as sexy or dramatic as a hammer, saw or vice grip to a construction worker BUT to people being invited into a world they're not familiar with they become a welcome mat on the floor to a journey.
It's accurately portrayed. At the same time, it's not the center of the story. That is still the human component.
They spent a lot of time/effort in "Saving Private Ryan" getting the sound of the M1 clip ejection right. But nobody ever comments on or explains this in the movie.
Veterans watching the movie said they "got that right".
(I'm not saying that "Saving Private Ryan" doesn't bend reality in some ways for the sake of the story. But they didn't... have Rambo take out a platoon with his bowie knife.)
("Band of Brothers" is another good choice -- the mini-series precursor to "Saving Private Ryan".
Then there are, for example, some of the older, somewhat spartan but impactfully understated British films, whose titles I can't think of right now. It was actually films like these that I was thinking more of, when I started writing this, before those contemporary items came to mind.)
If done properly, such portrayals can convey a quiet, authoritative air that is actually more convincing than some of the "explained"... "exaggeration" and/or simplification that exists in many movies including some big budget production.
Aiding this might be spending some time actually explaining these things, in some depth, to the actors, so that they can portray them with some understanding, rather than simply parroting the script.
Of course, you might have to convince/sell a potential purchaser/producer on this idea, to help the technical content go down.
P.S. I should probably shut up, now.
But, I think there is something to an accurate portrayal that is the richer for not being too self-conscious (on screen).
P.P.S. A few random films, with different topics, where this might apply, that I'm happening to think of upon this unplanned attempt to come up with some relevant examples.
"China Syndrome" (although I'm a bit hesitant, having only seen this with commercials and while somewhat distracted)
"Traffic" -- the older, European mini-series version, from the 1980s
Watch "Eat Drink Man Woman" and see how much of a feel for 90's (upper classs-ish) Taipei you walk away with. (Although, admittedly, as I understand it Ang Lee brings a certain outside or cross-cultural perspective to it from his having spent significant time abroad.)
There are probably many better examples, but that's what my tired mind can dredge up, at the moment. And I think this represents a variety of things where authenticity enhances rather than confuses or degrades.
P.P.P.S. See P.S., above. ;-)
I don't have a list at hand and may not be the one to provide one. But... you might look around and cross reference comments to find the "quintessential" works on these topics.
One exceptional book can be worth (more than) a car load of the alternatives.
1) films often use the "aha, now I'm really serious" gimmick, wherein the "hacker" is now talking about some technique that he hadn't used before. There are rarely authentic justifications for this in reality. See, for example, the last 20 minutes of "Swordfish" ... "That's 2048 bit RSA... not even I could crack that!". Please don't do that.
2) Anecdotal: the best hackers I know shun jargon. Jargon-heavy dialogue always feels condescending. Anywhere you feel tempted to use impressive-sounding jargon, consider that the hacker would consider such a thing commonplace and would consider it implicit in any conversation with another hacker. Another analogy: you wouldn't write Bruce Lee in a role where he expounds in detail about his punches and kicks as he's fighting; apply the same aesthetic and you'll do fine.
3) The technical details of "Hacker Speak" are almost impossible to make authentic to your audience because there are so many different specializations. I could wax on about, e.g., high performance numerical computations but wouldn't know how to synthesize authentic talk about cryptography. On the other hand, I would probably be able to pick out inauthentic talk about cryptography pretty easily. Spotting fakes is a lot easier than creating plausible technical dialog. My recommendation would be to elide as much of the technical story as possible, and focus any programming-related dialog on the "three chief virtues" of a programmer: "laziness, impatience, and hubris" (coined by Larry Wall, I believe). To put it in more accessible terms: your hacker should always be thinking "How can I accomplish this task with the least human work possible (laziness)? How can I engineer it to go faster (impatience)? Is there really any reason why I couldn't write a program to solve problem X (hubris)?"
Anyway, I've had some experience with the film/TV industry (lived in LA for many years) so if you have any specific questions I'm happy to expand in email (see my profile for my address).
Good luck!
You will need a fairly exceptional consultant for the brief and lucid explanation.
Your job, as the screenwriter, is to fit that explanation into the screenplay in a manner that seems natural and furtherw the storytelling.
Then, you get an audience that learns a bit, and experts who say to themselves, "Hey, they actually got that bit right." (Maybe they're even quietly impressed at that. And when their friends ask them what movie gets "X" right, they're more likely to cite yours.)
A lot of Hollywood screen-writers use computers as a form of magic to get around plot difficulties. Say your heroes meet a bunch of aliens and you don't want to dedicate a 30 second montage to the months or years-long process of a team of linguists learning to communicate (badly) with them. Have your hacker set up a nice translation program on his special unobtanium-core uber-computer and, presto! When those aliens turn out to be not so nice, again the hacker can save the day by slicing into their mainframe and blowing up their mother-ship with a mac virus!
You get the idea.
You can pick up all the hacker language you want, but if you don't pick up some real knowledge (or run your plots past real hackers) you're going to make the same mistakes practically every other Hollywood screenwriter does.
There's actually been quite a lot of success demonstrated with hacking automotive control systems. http://www.pcworld.com/article/196293/car_hackers_can_kill_b...
The steering isn't drive-by-wire, but everything else in a modern car is (including accelerator and brakes).
To see hackers in action, look for footage of "capture the flag" type events. In practice, it's usually just a bunch of guys typing on keyboards and scratching their heads without saying much.
:)
Unfortunately, now you have two problems. Sorry.
Now, if you only have a day to spare for the project, that's a different story altogether.
Good luck!
thanks for your time.
From the Jargon File ("Around 1988"[0]):
HACKER [originally, someone who makes furniture with an axe] n. 1. A person who enjoys learning the details of programming systems and how to stretch their capabilities, as opposed to most users who prefer to learn only the minimum necessary.
2. One who programs enthusiastically, or who enjoys programming rather than just theorizing about programming.
3. A person capable of appreciating hack value (q.v.).
4. A person who is good at programming quickly. Not everything a hacker produces is a hack.
5. An expert at a particular program, or one who frequently does work using it or on it; example: "A SAIL hacker". (Definitions 1 to 5 are correlated, and people who fit them congregate.)
6. A malicious or inquisitive meddler who tries to discover information by poking around. Hence "password hacker", "network hacker".
If were talking one through four, you can probably just look at talks by open source project leaders at various conferences. Take a look at various bulletin boards, etc.
If were talking 6, then I would like to add that in my experience the speech used generally changes with skill and age. The security experts I've met, who seemed worthy of the title, seemed to have a very sophisticated sort of tone, almost formal. But I don't have very much experience in this area.
Though I agree with SiVal, minute for minute, research spent on technical accuracy will translate into more believable dialogue on stage than anything else you could do. If you want to hear a phreaker talk about how he became a phreaker for three hours, these tapes will be perfect for you:
ftp://ftp.wideweb.com/GroupBell/HowBPhreak1HQ.zip
ftp://ftp.wideweb.com/GroupBell/HowBPhreak2HQ.zip
ftp://ftp.wideweb.com/GroupBell/HowBPhreak3HQ.zip
ftp://ftp.wideweb.com/GroupBell/HowBPhreak4HQ.zip
ftp://ftp.wideweb.com/GroupBell/HowBPhreak5HQ.zip
ftp://ftp.wideweb.com/GroupBell/HowBPhreak6HQ.zip
What year is the story taking place? That's relevant because the terms you might hear today are not the terms you would hear in 1975, or the terms you would hear in 1988.