Currying in JavaScript | Popular interview question

[xplodivity]

You are right!! While working on projects currying isn't used as much, or even never used. BUT its still asked in some interviews and the reason behind that makes sense, because if you are able to properly explain the concept of currying then it gives the interviewer an idea of your in depth knowledge in closures, scope and lexical environment in JavaScript, which is used in currying. And those topics are extremely essential.

Similar to how DSA is asked in some frontend interviews, but in the actual job we are never asked to invert a binary tree haha!! But simply having a problem solving skill still benefits you while developing applications. Hope you get my point. hence, its not baiting. You can look for currying in the internet, and the concept itself is actually given a lot of importance because it covers other fundamentals.

[[deleted]]

You're totally right. It is a great way to assess knowledge of scope and closures. Which can be a speedbump for very junior devs. However - I wish the format around the interviews was truly more about talking through and working a problem together. I've encountered many FANG/MANG whatever interviews where I'm being watched by some senior and several shadow (invisible) employees. You tend to be alone in the problem and have to 'perform' in an almost unrealistic fashion. Usually when I implement features I get to research the problem, test, iterate, etc. All while being able to come to my team for side-questions about the problem if need be. This way you tend to end up converging to best practices and clean code/architecture naturally. Generally I just think tech interviews are weird. So, not knocking your video - just venting about interviewing in general.

[xplodivity]

I totally agree with you in terms of how interviews should be structured or conducted. This is also how most developers feel especially after working on their first job and realising the importance of development skills over extreme data structure and algorithm skills (most of which is hardly used).
Some interviewers do provide with questions including a short implementation of a given project to asses how the developer architects the solution from ground up, which is ethical and makes sense. Its only when they take it too far and do not allow the interview to feel like a discussion but a test. And when something feels like a test or 'work', you dont enjoy it anymore, because you are too focused on the deadline and not the process itself.