Re: [Lit.] Buffer overruns
From: Hank Oredson (horedson_at_earthlink.net)
Date: 02/02/05
- Next message: Anne & Lynn Wheeler: "Re: [Lit.] Buffer overruns"
- Previous message: Andrew Swallow: "Re: [Lit.] Buffer overruns"
- In reply to: Randy Howard: "Re: [Lit.] Buffer overruns"
- Next in thread: Brian Inglis: "Re: [Lit.] Buffer overruns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 02 Feb 2005 19:25:49 GMT
"Randy Howard" <randyhoward@FOOverizonBAR.net> wrote in message
news:MPG.1c6ae01d212fc2dc989eb2@news.verizon.net...
> In article <HqudnYXdq56ceZ3fRVn-iQ@comcast.com>, tlj3@comcast.net says...
>> infobahn wrote:
>>
>> > I continue to be surprised by your apparent antipathy to the concept
>> > of quality. If you are content for your programmers to produce inferior
>> > software, you should not be too astonished if they continue to
>> > *produce* inferior software. No wonder you are so much in favour of
>> > ABC! Have you even considered the *possibility* of hiring people who
>> > know what they're doing?
>>
>> While I agree with most of your points, I think this is unfair. How are
>> we to tell who to hire? More importantly, how do we tell who _not_ to
>> hire?
>
> Well, you might start by asking *real* interview questions. The type that
> most hiring managers are unqualified to ask, and most peer interviewers
> are
> afraid to ask, for fear of being rude or "too tough".
>
> There was a time when you had to *prove* that you know what you were
> talking
> about. Now, lying on the resume, followed up with a bunch of softball
> interview questions seems to be the norm. No wonder people are not hiring
> the appropriate candidates.
>
> Some examples of stupid interview questions:
>
> 1. Tell me about a time when <something bad happened on the job> and how
> you resolved it.
> 2. So, why did you leave your last job?
> 3. So, why do you want to join this company?
> 4. What books do you read in your free time?
>
> etc., etc.
>
> Instead of, "Here is an editor, compiler and linker. Let's write some
> code..."
At one job interview things seemed to be going quite well.
I was an obvious good fit for the position, the company seemed
to have a reasonable environment, the first few people I met appeared
to be capable and knowledgable. Just before lunch, in answer to
some specific technical questions about the work I was doing,
the interviewer suggested I might give a short talk on that work.
I said sure, why not, but that I did not have slides, reference notes,
etc. so it would be off the cuff. She said ok.
After lunch we walked over to a conference room. There were
about 20 people present. I spent an hour doing the presentation
and answering lots of very pointed questions. Got a real good
sense of what kind of people inhabited the team I would work with.
Did not take the job. Got a better offer from a different company.
> Of course, the latter is more difficult to conduct, particularly if the
> interviewer is clueless (as is often the case), and I've even heard people
> say that it is insulting to ask a professional to prove they are a, in
> fact, a professional.
Arghhh! Political correctness run rampant.
> People interviewing a programmer, to work for example on a device driver,
> never once ask them to explain or demonstrate *anything* about device
> driver programming for the intended target platform during the course of
> an all-day interview schedule. If it says so on the resume, it must be
> true.
And the references may well have backed up the claims, unless
you spent enough time on the phone to figure out if they were
telling the truth ...
-- ... Hank http://home.earthlink.net/~horedson http://home.earthlink.net/~w0rli
- Next message: Anne & Lynn Wheeler: "Re: [Lit.] Buffer overruns"
- Previous message: Andrew Swallow: "Re: [Lit.] Buffer overruns"
- In reply to: Randy Howard: "Re: [Lit.] Buffer overruns"
- Next in thread: Brian Inglis: "Re: [Lit.] Buffer overruns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
