James Newton wrote:
>I would rather see a few questions about debugging.
[...]

I think these tests are more appropriate for another test (micros/PICs), and 
since personally I would prefer to answer them orally (since the answers 
will likely be rather wordy).

> "Given a system that fails consistently in actual operation but operates
> correctly as soon as it is attached to a test fixture, list some methods 
> you
> might employ to find the problem."

Hm, I'd be curious to know the answer to this one, myself! :)

> "The only tools you can have to debug a project are an LCD panel (parallel
> interface) or a single logic probe with pulse mode. Which would you 
> select?"

Both? Isn't this application and problem dependent?

> "You are asked to recommend a microcontroller for a low quantity system 
> that
> will be used in house only. Do you select a chip with all the required
> hardware on board, or "bit bang" the few interfaces needed via software 
> and
> specify a lower cost chip with less onboard peripheral hardware? What if 
> it
> was a high quantity system for sale to a large market segment?"

This sounds almost too easy, but I see the value in it. :)  It's kind of 
like the question on an application I filled out once, "It is OK to steal 
from the company if everyone is doing it. True or False?"

Some people are really that dumb, and it's good to have these sorts of 
questions to quickly weed them out.

> "If you are hired as a contract programmer for the initial coding of a
> project that is expected to have a long life and possibly many revisions,
> would you choose to write the code in a commonly available language with
> which you are less familiar or with a little known language which you have
> used many times in the past?" (no right answer to that one, but it will be
> an interesting conversation)

What would you look for, in their answer?

> "During the development of a proprietary application in the workplace, you
> hit upon a unique way of solving a common programming problem which does 
> not
> directly relate to the project. Will you A) publish the snippet B) Ask 
> your
> boss if you can publish the snippet C) not mention the solution to anyone
> but use it again at this or other jobs in the future."

Not enough information?


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist