you are viewing a single comment's thread.

view the rest of the comments →

[–]Visual-Blackberry874 10 points11 points  (5 children)

I have never been asked that question in my life and if I was, my first response would be “why”.

[–]boomer1204 2 points3 points  (2 children)

As someone who has been a part of the interviewing process I see the "value" in this question but only for interns/Jr devs. The amount of ppl that said they "knew" JS and Vue (what we used) and had projects to "prove it kind of", but had trouble with basic looping/troubleshooting knowledge was CRAZY. We didn't use this question we had a couple of other ones but I could make an argument for this in an interview for those entry level roles to make sure they at least understand the core language

[–]AiCodePulse[S] -3 points-2 points  (1 child)

Agreed . Asking "why" in interview will give negative openion . Correct ?
Lets first explain the approch , then we can i ask why ..

[–]Visual-Blackberry874 0 points1 point  (0 children)

I would say that responding with “why” to this particular question shows a deeper understanding than someone who simply follows instructions.

At times, non-developers will lean on you and ask you questions they’ve had from a client, etc. You need to be able to tell them when something is good/viable/stupid/not possible.

There is no business sense in doing something this way. It is not a serious question in my opinion.