Sat, 24 Jan 2004


to grok


clearly, I have too much time on my hands. or, more tragically, instead of doing things I need to do, I sit her mentally masturbating as usual. (notice the word mental.)

anyway, I was thinking of the word "grok" for some reason. for those who aren't into science fiction and therefore have never read the book Stranger in a Strange Land by Robert Heinlein, well, that's where it comes from. in the story, it's of Martian etymology, meaning literally, "to drink," and figuratively, "to understand deeply." well, of course, the latter connotation inevitably seeped into geekspeak, but the crazy thing is that I think it is beginning to spread into the mainstream. of course, this might just be a reflection on how much more technological our world is (read as: how much more acceptable—nay, perhaps necessary—it is to be a geek—I have to say it: it has become chic to be a geek—OK, well, maybe not....), and, of course, I was in Silicon Valley when I heard a non-computer science person use it, so maybe it was a meaningless occurance. nonetheless, it is in some general dictionaries (post-Y2K, granted.) and, I might add, it is quite a useful word.

I then turned my thoughts to the word "savvy," not in its adjective form, but in its verb form. I'm not sure if it really is standard pirate argot, but Johnny Depp certainly used it a lot in "Pirates of the Caribbean", and even at least once in "Once Upon a Time in Mexico". What I figured out, then forgot, then looked up is that it is derived from the Spanish word "sabe," which means to know.

anyway, back to "grok." there are a few related geekspeak terms (which, by the way, I've never really heard before) such as "glark","glork", and "zen," again, not as an adjective, but as a verb.

well, enough of that for now.

19:32:29 24 Jan 2004 > /language > permalink > 0 comments

Sat, 01 Nov 2003


semantic relativism


Taxonomy is a boundary object.

This blog post talks about how we shouldn't jump down other people's throats when they get the definition of some jargon (for example, "taxonomy" or "object") wrong. With this, I agree.

But the gist I start getting is that it's OK for a single semantic element to be "overloaded" with multiple meanings. Which I think is confusing.

Still, context is key. If a programmer says something, chances are, it will be different from when a suit says something.

Maybe I'm misreading it anyway, but I think it is important to keep these distinctions there. The way I see it, semantic elements need to either converge or diverge. We cannot propagate a multiply overloaded semantic element and expect everyone to just accept it without critical analysis.

Convergence: Ideally, while you might use the same semantic element and mean wildly differing things, if you are serious about communication, you will, at some point, have to statically define your terms. While the meanings of semantic elements will definitely drift with time, you cannot use this drift as an excuse not to nail down whatever you are talking about. While I agree that overloaded semantics are good conversation starters, you can't just leave at that. At some point, things need to be made concrete. Often times, this requires creating new terminology, because the original semantic element will have become so overloaded that it will become meaningless.

Divergence: Chances are, however, you will fail to converge on a single meaning. At this point, it is important to differentiate clearly and, again, define your terms unambiguously. As above, there needs to be a distinction between what a programmer means and what a suit means. While there is no need to create completely different terminology, and it is acceptable to keep a term overloaded, it is important that you can easily contextualize what it means.

But don't get me wrong. I understand fully well that the meanings of semantic elements drift with time. Words are not static. But words are not meaninglessly fluid either. Words are objects that exist in space and time, and in truth, words represent tree structures. Meanings are always related somehow, however non-obvious, and there must be a common branch point. This is where you must come from to start defining your terms. Context will allow you to hone in on the correct meaning.

This is precisely how language operates, in a truly democratic fashion. You cannot create useful words by fiat. The transaction of semantic creation requires one to utter the word, and the other to grok it, and if the other does not grok it, then you have failed and you must try again. I agree, language is really constant negotiation between interested parties.

In sum, all I'm trying to say is that while words cannot be arbitrarily tossed around and expect to be meaningful, words are also not necessarily tied to some Platonic ideal. Admittedly, on a physical level, the sound waves translated by different individuals' cochlear nerves will activate wildly varying neuronal pathways, and understanding requires a committment to be willing to fine-tune, until both sides are adequately satisfied that they mean roughly the same thing.

10:44:17 1 Nov 2003 > /language > permalink > 2053 comments