4 ms·
I dunno. The thing that sold it for me was this assertion: Q. Look, I’m sorry if you feel put-upon here, please don’t get hostile. I’m just trying to get
by gchpaco 17y ago
I dunno. The thing that sold it for me was this assertion:
Q. Look, I’m sorry if you feel put-upon here, please don’t
get hostile. I’m just trying to get a clear picture of the
specs I need here. Obviously if I’m going to write a file
copy method, instead of using one of the many extant file
copy routines in various libraries and frameworks, it’s
going to be fulfilling a specialized set of requirements,
and I’m going to need to have good answers for these
questions. If you want, I can hack something together in a
minute, but I’d have to note that there were many
unresolved issues as to requirements and purposes.
- swolchok 17y ago"The candidate has a myopic focus on documentation and best practices, as demonstrated by his failure to apply a simple solution to a simple problem. No hire."
- xsmasher 17y agoI'd say pedantic and difficult to work with, but agreed, no hire. The correct answer would be to write a simple solution and note your assumptions and point out the edge cases - but not in such an antagonistic manner.
- philwelch 17y agoThe problem is, this is exactly the same kind of argument you'd hear from someone whose programming ability extends merely to the ability to string together API's, or from MIS students who don't understand the point in learning how to write a compiler or OS kernel. Alternatively, you also hear the same thing from the types of people who want to sit down and gather ALL the requirements before writing a single line of code, rather than just prototype and iterate.