So "pictacious" is a perfectly cromulent word now?Anyhow, the question you have to ask about any kind of language play is what it adds to the story. I'll illustrate with my current WIP, then explain what I hope the jargon accomplishes.
In my current WIP, the characters use nautical terminology to refer to their spacefaring equipment. This tendency starts out modestly: small spacecraft are "boats" and large ones are "ships". The floors inside a spacecraft are "decks" and the walls "bulkheads". Within the craft one orients oneself "abaft" (toward the "stern"), "ahead" (toward the "bow"), to port or starboard or generally "abeam", or perhaps "aloft" or "below".
One "boards" a small military ship or boat through an airlock, but large passenger vessels are boarded via a "companionway". In the same way the age of powerboats borrows and redefines many terms from the age of sail, the age of spacecraft redefines terminology from the age of surface boats. For example a below deck storage area is called a "chain locker" if "gear" can be deployed from it outside the hull, or a "lazarette" if not.
Now this is all set-up. The jargon really reaches a crescendo during action scenes. Some of it is copied, some adapted, and some cut from whole cloth, but it is all (I hope) carefully introduced so that it is understandable in context.
For example our hero-protagonist scout captain and her ex-husband launch the ship's "pinnace" to make a "landing" on an unexplored planet. They're unpleasantly surprised to find an unfriendly "frigate" has launched an "interceptor", which is "inserting into our de-orbit on our lee side". The ex-husband (a former navy man) remarks that he's often put a gunboat ahead of a target on the same landing approach trajectory in order to keep the target from "running downwind and losing us over the horizon."
The wily captain announces that she intends to "heave to and lay her down on her tail," so it will the interceptor that will pass over the horizon and thus lose track of them. The ex then cautions that they are approaching too "hot" to land so steeply. They ought to orbit the planet at least once before landing for safety.
A (hopefully) nail-biting "thruster duel" ensues, a game of chicken in which each pilot vies to "carve" the steepest approach he can without having his boat burn up on reentry like a shooting star. Of course the interceptor's pilot doesn't have Kate's nerves of steel; he chickens out and she wins the thruster duel.
When they make landfall and the captain inspects the "main propulsion truss" for damage, she finds that fuel has been sprayed on the "aft pressure bulkhead". A "pinhole" has developed in the fuel line which makes "arming" and "igniting" the thrusters in an oxygen atmosphere dangerous. The captain explains this to her ex because as a navy man he wouldn't know this due to his limited experience "dirtside"; it would be perfectly safe to arm and ignite the thrusters in space. The squabbling but still romantically attracted couple are now marooned on an alien planet, possibly for eternity.
Now using jargon this way is risky; I certainly wouldn't use it until I was far enough into the story to be reasonably certain the reader was committed to the fate of the characters. It's also a chore, because every bit of that jargon has to be made understandable in the context of the scene without recourse to providing a glossary. That also means that every bit of jargon has to have a meaning that's meticulously worked out. And it's entirely unnecessary. Since I have to make everything clear in plain language anyway, the jargon is quite superfluous.
This for me is experimental. I've done similar things in the past for comic effect, but in this case I want the readers to feel they've got a window into a plausible world, that they are looking over the shoulders of characters who have experiences and accomplishments that are exotic, yet understandable. None of the details actually matter, except insofar as they make the reader feel like part of the club, which won't happen if the jargon isn't made clear in context.
[This message has been edited by MattLeo (edited August 10, 2011).]