From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <285f606db6bcbbfc31f0a9f8cdf04593@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rc mystery
Date: Fri,  6 Aug 2004 00:12:33 -0700
From: Skip Tavakkolian <9nut@9netics.com>
In-Reply-To: <20040806135100.5333c6df@garlic.apnic.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: d176de4e-eacd-11e9-9e20-41e7f4b1d025

>>> if so, keep a watchful eye on your C compiler!
>>
>>yup. one of my favorite C interview questions (in the form of an example)
>
> Certainly, after I proved myself unable to code in FORTRAN having
> mistakenly claimed so, back in  '81, in front of an interview panel of 10
> people at the UK antartic survey offices, I learned very quickly that
> truth hurts less than some lies. this may justify your point of course. I
> remain deeply ashamed at my dishonesty and stupidity, in many dimensions
> in this case.

I don't know if it comes from dishonesty or just not knowing because
one isn't regularly challenged about how well one really knows subject X.

>
> But, don't you think there is something equally deceitful in setting trick cyclist
> tests on people?
>

What's deceitful about asking somebody what does printf("%c\n",0["unix"]);
print and why?  The "trick" is only a conversation piece.

Having been on the receiving end of it too, I sympathize; but I think
it is a fair way to weed out some of the posers (with a degree or not).  I
agree with what geoff said.  Code samples of previous work are probably
more representative of one's true abilities.