[gameprogrammer] emotional miscues, was Re: Re: software engineering

Why don't we all just take a deep breath and let go of the whole thing.

This exchange is a prefect example of emotional miscues in email
communication. It is sooooo easy to read emotional intent into email
that you would never get in a face to face conversation. It gets much
worse when the people involved come from different cultures and even
worse when dealing with communication in a language that is not your
"birth" language. (I don't know if all or any of those came into play
here.) And, even the difference in the time of day between where you are
and where the other person is can have an effect on the emotion response
to a simple piece of text.

So, how does it effect games?

                Bob Pendleton

On Fri, 2004-09-24 at 10:30, Alexander Sabourenkov wrote:
> Justin Coleman wrote:
> > On Fri, 24 Sep 2004 18:20:03 +0400, Alexander Sabourenkov
> > <screwdriver@xxxxxxxxx> wrote:
> > 
> >>For some obscure reason, all links on the first page of google results for
> >>'second system syndrome' pointed to more-or-less exact definitions.
> > 
> > 
> > Thanks so much for your quick and accurate, if condescending, answer.
> > You're so right, every time an unfamiliar term comes up I should
> > immediately google for it. There's no better way to look educated in a
> > job interview than to respond to an interviewer's questions with,
> > "Could I borrow a web browser for a few minutes to look up the answer
> > to that?"
> 
> I'm sorry you took my words as being hostile. They were but a pointer to the 
> data.
> 
> > I am well aware of the various search sites available on the web. I
> > chose to eschew them in favor of the opinions of people who I feel are
> > more competent in the subject than myself, in order to increase my own
> > level of competence in the subject. If it was just one term, yes, I'd
> > look it up in google. However, being the logical person I am, I made
> > the deduction that if I didn't know the meaning of *one* software
> > engineering term, that it's entirely possible there might be *other*
> > terms I don't know as well. Now, of course, that being the case my
> > choice is reduced to A) look up each term individually, or B) ask
> > people who know what they're talking about (like Bob Pendleton and
> > others on this list) to recommend a book with lots of terms in it,
> > that I can learn all at once, not coincidentally absorbing the
> > relation between all the terms as well.
> 
> As Chris Shnurr pointed out, it is not the knowledge of facts that matters, 
> it 
> is the mastery of finding information.
> 
> Upon reading Bob's message I also wondered, what the term may mean. And I 
> found out the answer, with pointers to origin, related terms, and sources of 
> info in about 15 seconds, as compared to more than hour this discussion has 
> already taken.
> 
> Of course if you wanted to socialize rather than have a concrete answer to a 
> concrete question in minimal time, that's whole another matter.
> 
>  >
>  > Perhaps you could suppress your hostility long enough to suggest a
>  > book, as I originally asked?
>  >
> 
> I see you've got plenty of time for writing texts this long, why haven't you 
> got two seconds to cut'n'paste the term into searchbox and hit the button?
> 
> 
> And before you take that for another grave hostility towards you,
> 
> please don't.
> 
> I sincerely apologize for that I could not keep myself from writing my first 
> reply to you and suggesting using Google. I really should have left that to 
> others.
-- 
+--------------------------------------+
+ Bob Pendleton: writer and programmer +
+ email: Bob@xxxxxxxxxxxxx             +
+ blog:  www.Stonewolf.net             +
+ web:   www.GameProgrammer.com        +
+--------------------------------------+



---------------------
To unsubscribe go to http://gameprogrammer.com/mailinglist.html

Other related posts: