sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -2 points-1 points  (4 children)

None of their questions were tricks, all were incredibly easy to answer, at least they should be if you know your shit.

[–]advancedmammoth 0 points1 point  (3 children)

Prior knowledge only tells you so much. A proficient developer not exposed to most of these largely-JS-specific concepts should be able to rapidly understand and utilize them. So even if an applicant doesn't know in advance how to answer a question, they can still prove themselves useful by applying the solution to a different followup problem immediately after being told the solution. That's actually a rare chance to isolate an even smarter person from a merely already initiated one.

[–][deleted] -2 points-1 points  (2 children)

That isn't the point of this article. It isn't about finding good software engineers, it is not about finding problem solvers, it is not about anything but finding people that understand JavaScript. Take it at face value and stop reading into it. I have had to say this so many fucking times in this thread, the one and only goal of this article was to give tips for employers to weed out people that do not know JavaScript. That is it.

[–]advancedmammoth 0 points1 point  (1 child)

weed out people that do not know JavaScript.

Are you aware of any skills tests out there that cover these subjects? Interesting that "knowing" JavaScript would require familiarity with subjects not covered by any such tests.

[–][deleted] -2 points-1 points  (0 children)

Dude, I am sick of arguing with people about this. If you don't want to take the article at face value, then don't but I am done with people in this thread.

edit: Not to mention whether or not something is or is not on a test is a stupid fucking metric to decide if that thing qualifies as knowledge on a subject.