4 ms·

If you don't know the difference between sync and async you're not qualified to solve problems with any realistic level of scale (>10 concurrent users which is

If you don't know the difference between sync and async you're not qualified to solve problems with any realistic level of scale (>10 concurrent users which is a very low bar) or complexity (have you really never had to code logic that uses 2 or more concurrent network calls?). Might be excusable for a junior engineer but definitely not someone who describes themselves as senior.

vmception 5y ago
you google it and understand it or re-understand it in 5 minutes after trying 20 iterations in the IDE. thats representative of the job, so it should be represented in the interview. open book interviews test for resource finding and implementation skills.
- e4e78a06 5y ago
  You shouldn't have to google a basic concept that, if you truly were senior level, you would be using on a daily basis. This is not some obscure language syntax or feature.
  - vmception 5y ago
    They shouldn't be penalized for it either, using reference should be a force of habit. The main problem with your response is that the threshold for "basic concept" is arbitrary by framework, by language, by time, by interviewer. Revert back to interviewing things relevant for the day to day job, look at what developers actually employed there did over the last few weeks, and interview on that.
    - e4e78a06 5y ago
      Knowing the difference between async and sync is relevant to any JavaScript developer's daily tasks. If you are hiring a JavaScript developer it's 100% a fair question to ask. If you are hiring a generalist maybe not, but if they have JavaScript experience in the last 3 years listed on their resume, I again say it's fair to ask. Asking about async/sync in JS is completely different from asking someone what obscure features like finalizers are in Java. One is used on an hourly basis when writing code, the other one is never used except in obscure legacy code. If you do what you're proposing and just ask about projects I think you'll find it's easy for incompetent people who are floundering around and copy pasting from stackoverflow without understanding what they're copying to pass your bar. I copy from stack overflow all the time but I understand what I'm copying and why it works and when it doesn't work.
    - Hermitian909 5y ago
      > Revert back to interviewing things relevant for the day to day job, look at what developers actually employed there did over the last few weeks, and interview on that. `async` questions are the most day job relevant questions I can imagine for a javascript developer. It is so pervasive, a such a simple piece of syntactic sugar over basic asynchronicity, that not knowing it is damning along a number of axes.
- TheCoelacanth 5y ago
  If you have made it through multiple years of building UIs without ever needing to google that, then you must have a profound lack of curiosity. You can certainly stumble your way to a semi-working app without knowing that, but your mental model of how Javascript works is fundamentally lacking if you don't know that.
  - vmception 5y ago
    its still about the syntax and referencing that, there are like 3-5 ways of doing asynchronous code in JS and its also not my point about "async in JS", thats a symptom in a field where ever random person pulled in to conduct an interview has their own random threshold of competence, when simply conducting an interview that mimics the day to day on the job would be more accurate "did you google that in 10 seconds" great! "did the compiler autocomplete your method name or show you a list of likely possibilities?" great! "did you post a question on a QA website, while you went to work on other parts of the task while the hints and answers rolled in?" efficient! "did your compiler show you a syntax error immediately that you corrected immediately?" great! "did you compile it as you went and rapidly iterate towards the write answer like everyone else working here?" perfect! whiteboarding, and most collaborative coding platforms, fail to replicate 9/10ths of that. so it tells nothing about the candidate.

vmception 5y ago

you google it and understand it or re-understand it in 5 minutes after trying 20 iterations in the IDE. thats representative of the job, so it should be represented in the interview. open book interviews test for resource finding and implementation skills.

e4e78a06 5y ago
You shouldn't have to google a basic concept that, if you truly were senior level, you would be using on a daily basis. This is not some obscure language syntax or feature.
- vmception 5y ago
  They shouldn't be penalized for it either, using reference should be a force of habit. The main problem with your response is that the threshold for "basic concept" is arbitrary by framework, by language, by time, by interviewer. Revert back to interviewing things relevant for the day to day job, look at what developers actually employed there did over the last few weeks, and interview on that.
  - e4e78a06 5y ago
    Knowing the difference between async and sync is relevant to any JavaScript developer's daily tasks. If you are hiring a JavaScript developer it's 100% a fair question to ask. If you are hiring a generalist maybe not, but if they have JavaScript experience in the last 3 years listed on their resume, I again say it's fair to ask. Asking about async/sync in JS is completely different from asking someone what obscure features like finalizers are in Java. One is used on an hourly basis when writing code, the other one is never used except in obscure legacy code. If you do what you're proposing and just ask about projects I think you'll find it's easy for incompetent people who are floundering around and copy pasting from stackoverflow without understanding what they're copying to pass your bar. I copy from stack overflow all the time but I understand what I'm copying and why it works and when it doesn't work.
  - Hermitian909 5y ago
    > Revert back to interviewing things relevant for the day to day job, look at what developers actually employed there did over the last few weeks, and interview on that. `async` questions are the most day job relevant questions I can imagine for a javascript developer. It is so pervasive, a such a simple piece of syntactic sugar over basic asynchronicity, that not knowing it is damning along a number of axes.
TheCoelacanth 5y ago
If you have made it through multiple years of building UIs without ever needing to google that, then you must have a profound lack of curiosity. You can certainly stumble your way to a semi-working app without knowing that, but your mental model of how Javascript works is fundamentally lacking if you don't know that.
- vmception 5y ago
  its still about the syntax and referencing that, there are like 3-5 ways of doing asynchronous code in JS and its also not my point about "async in JS", thats a symptom in a field where ever random person pulled in to conduct an interview has their own random threshold of competence, when simply conducting an interview that mimics the day to day on the job would be more accurate "did you google that in 10 seconds" great! "did the compiler autocomplete your method name or show you a list of likely possibilities?" great! "did you post a question on a QA website, while you went to work on other parts of the task while the hints and answers rolled in?" efficient! "did your compiler show you a syntax error immediately that you corrected immediately?" great! "did you compile it as you went and rapidly iterate towards the write answer like everyone else working here?" perfect! whiteboarding, and most collaborative coding platforms, fail to replicate 9/10ths of that. so it tells nothing about the candidate.