B
bitrex
Guest
On 11/5/2020 6:45 PM, Don Y wrote:
Basically the problem is that as stated the original question is too
trivial to be able to deduce much about anyone\'s true software design or
programming or whatever you want to call it, ability.
It\'s a lousy question in isolation that doesn\'t reveal much other than
to weed out total non-hackers, or to (unjustly IMO) weed out someone who
doesn\'t know or can\'t remember the closed form that day but otherwise
wrote some code that did what was required.
Making it part of a larger problem where one might have to write an
algorithm or function that computes such a sum, as a component of a
larger task, would be more enlightening when someone\'s particular
solution to the sub-problem is viewed in a context.
If say the goal was to do the more complex task in a timeframe and the
code is otherwise good and comes in under the time limit but they use
that solution to basically get-r-done and didn\'t sit around wasting time
trying to remember a formula then that seems sensible.
On 11/5/2020 2:38 PM, bitrex wrote:
[This is why you want an interviewee who asks questions instead of just
picking up a pen and writing down the first (only?) solution that comes
to mind.]
A solution that well-satisfies the stated requirements of the problem
but doesn\'t satisfy some further unstated requirement that turns up
later is just the kind of client or employer you may not want to work
for and is something that is complained about with respect to
questions asked here all the time.
If the potential employer changed the goal-posts during/after the problem
was posed, you can simply condition your answer based on that additional
information.
Telling an applicant to sort a list -- and, LATER, telling him that the
items in the list are 200 character strings -- can be used to force
the applicant to consider tweeks to his implementation when the cost
of \"moving\" an item is considerably increased. How he addresses this
shows that he understands the cost of copies, etc.
Basically the problem is that as stated the original question is too
trivial to be able to deduce much about anyone\'s true software design or
programming or whatever you want to call it, ability.
It\'s a lousy question in isolation that doesn\'t reveal much other than
to weed out total non-hackers, or to (unjustly IMO) weed out someone who
doesn\'t know or can\'t remember the closed form that day but otherwise
wrote some code that did what was required.
Making it part of a larger problem where one might have to write an
algorithm or function that computes such a sum, as a component of a
larger task, would be more enlightening when someone\'s particular
solution to the sub-problem is viewed in a context.
If say the goal was to do the more complex task in a timeframe and the
code is otherwise good and comes in under the time limit but they use
that solution to basically get-r-done and didn\'t sit around wasting time
trying to remember a formula then that seems sensible.