J4rG0|\|

Published July 05, 2011
Advertisement
[color="#111111"][font="Georgia,"][color="#111111"][font="Georgia,"]I remember being so excited about learning new things that I would often share my growing vocabulary with others. Of course, rattling off GPU model numbers and introducing my peers to my work with terms I made up made me feel smart, but it did limit my audience. I'm not just talking about an audience of middle-aged parents or users who ride the short bus, I'm including other geeks who actually knew what I was talking about.[/font][/color][/font][/color][color="#111111"][font="Georgia,"][color="#111111"][font="Georgia,"]
[/font][/color][/font][/color]
[font="Georgia,"][color="#111111"][size="2"]Human language is great for not just sharing ideas, but also putting them in perspective. Even some of the most brutal mindf&#*s like quantum phenomenon can be clearly explained in accessible ways by people like Dr. Michio Kaku or Dr. Richard Feynman. The interesting thing about these men is that they do not really describe systems and relationships separately based on their knowledge alone, they mix together their knowledge AND the knowledge of their audience to create a mutually beneficial message: The audience gets it, while the speaker enjoys a boost to their reputation (assuming they were accurate!).[/color][/font]
[font="Georgia,"] [/font]
[font="Georgia,"][color="#111111"][size="2"]I know that the point of speaking simply has been discussed since Einstein weighed in on it, but I really want to express my appreciation to people who don't use jargon, even when I understand it anyway.[/color][/font][color="#111111"][font="Georgia,"]
[/font][/color]
[color="#111111"][font="Georgia,"]I tried this "walking encyclopedia" shtick: A few years ago when I tried too hard to "sound smart" to a fellow developer I met in Starbucks. I remember referring to acronyms and taking care to spell each one out. I may as well have stood up, puffed out my chest and screamed "BOW TO MY SUPERIOR, HYPER-COMPRESSED VOCABULARY!" I later realized just how inhuman I sounded.[/font][/color]
[color="#111111"][font="Georgia,"]
[/font][/color][color="#111111"][font="Georgia,"]Since then, I get a little impatient when someone uses jargon because I genuinely want to hear what they have to say! Why am I being led down some linguistic detour that takes more work to listen to?[/font][/color]
[color="#111111"][font="Georgia,"]
[/font][/color][color="#111111"][font="Georgia,"]To illustrate how far this could go, I recently stumbled upon an interesting library, and the page describing it included this text (translated from French).[/font][/color][color="#111111"][font="Georgia,"]
[/font][/color][font="Georgia,"] [/font]
[font="Georgia,"][size="2"][color="#111111"][quote]A pipeline [/color][/font]P[color="#111111"][font="Georgia,"] is a chain of functions [/font][/color]F1[color="#111111"][font="Georgia,"] , ..., [/font][/color]Fn[color="#111111"][font="Georgia,"] such that P (x) = (Fn ? ... . F1) (x). Therefore, if the function F [/font][/color]i[color="#111111"][font="Georgia,"] defined by F [/font][/color]i[color="#111111"][font="Georgia,"] : E [/font][/color]i[color="#111111"][font="Georgia,"] ? S [/font][/color]i [sup][ 1 ][/sup][color="#111111"][font="Georgia,"] , then E [/font][/color]i +1[color="#111111"][font="Georgia,"] = S [/font][/color]i[color="#111111"][font="Georgia,"] and S [/font][/color]i-1[color="#111111"][font="Georgia,"] = E [/font][/color]i[color="#111111"][font="Georgia,"] . In other words, the output of F [/font][/color]i[color="#111111"][font="Georgia,"] is the entry of F [/font][/color]i +1[color="#111111"][font="Georgia,"] [/quote][/font][/color]
[font="Georgia,"] [/font]
[font="Georgia,"][size="2"][color="#111111"]This gets the point across, but it just does not seem necessary. Why assume that the audience is familiar with composite functions and basic set theory? If you are not in a formal setting that expects you to get technical, why is the below so dirty?[/color][/font]
[font="Georgia,"] [/font]
[font="Georgia,"][size="2"][color="#111111"][quote]A pipeline is a series of functions that are processed in a fixed order, where the output of each function is passed on to the next one down the line. The output of the entire pipeline is the output of the last function.[/quote][/color][/font][color="#111111"][font="Georgia,"]
[/font][/color]
[font="Georgia,"][size="2"][color="#111111"]When you write documentation, or are just plain trying to explain things to someone, how do you frame what you say or write? Is it better to communicate with people on your own level, or to make everything you say understandable to a ten year old?[/color][/font]
1 likes 3 comments

Comments

Zethariel
If everything would be explained so that a 10 yo would understand it, it would defeat the purpose of elite universities and degrees. People just want to be smart and sound smart. Jargon makes you part of a closed (or open) community of like-minded people. You use jargon to signalise you belong to them and share their ideals.

That is how I see it.
July 06, 2011 09:47 AM
zyrolasting
I went to Georgia Tech to talk to a chemist and quantum physicist today. I was thinking about changing my target career path, and admitted to both professors that I was currently unfamiliar with their work. Since our appointments seemed to be soon after they were busy with engineering projects, they used terms I was unfamiliar with.

Of course, this is not a bad thing at all! You are absolutely right to mention that more experienced people should demonstrate said experience where it matters. Since I (clearly) lacked experience, I did have to ask the profs to gear down the conversation enough to learn more about flaws I need to address before I could get a chance work with them.

But, even if I understood everything they said, I doubt that I would need to use a certain vocabulary all the time. Being both unambiguous and accurate is impressive, but it is also great to take complicated, relevant ideas and say them simply. I now think I was too quick to say that all messages should be understandable to a ten year old, so thanks for doubting that statement! [img]http://public.gamedev.net/public/style_emoticons/default/biggrin.gif[/img]
July 07, 2011 03:02 AM
Emmanuel Deloget
'lo,

There's a reason why I used a formal description of a pipeline: it's far more precise and concise than the same definition written in plain english (or in plain French in this case). The full definition of a pipeline is given by:

[quote]
A pipeline P is a chain of functions F1 , ..., Fn such that P (x) = (Fn ° ... ° F1) (x)
[/quote]

The remaining part is here to help.

If you want the same full description in plain English, you also have to talk about a myriad of pther thing, including input and output sets and so on.

Whenever I want to define something on my own blog, I tend to use a formal definition - or a definition which is as formal as possible.

Now, I agree: this makes the text more difficult to read (but then, I also speak of expression templates in that very post :))
July 21, 2011 08:16 AM
You must log in to join the conversation.
Don't have a GameDev.net account? Sign up!
Advertisement
Advertisement