4 ms·

Why interview questions are focused on knowledge? Because you want to hire someone that knows how to do things, not how to Google it or ask on Stackoverflow and

Why interview questions are focused on knowledge? Because you want to hire someone that knows how to do things, not how to Google it or ask on Stackoverflow and assemble bits and pieces of stuff wrote by others in a Frankenstein monster. Memory? It is not a test to write rare parameters correctly, the questions problem the knowledge about the most basic things in web development - html. It's like asking a surgeon in a hiring interview if he knows what a scalpel is; not the chemical composition or forging method, just what is used for. Imagine the guy saying "I don't know, I never memorize this stuff".

codeptualize 5y ago
How often do you write the html params and meta tags? I really don’t care if someone memorized all the meta tags. What matters to me is that if I ask them to write a template they can find out what they need to include according to the latest best practices and our situation. I rather have them looking it up than relying on something they memorized years ago and might be outdated. Looking things up is not the same as carelessly assembling as you describe it. It’s the ability to gather knowledge quickly, learn on the spot, so they can work on things they haven’t worked on before, and keep up with the latest best practices. Absolutely essential to FE development. And some of it is assembling and relying on tools to work efficiently; for example I would highly recommend to generate Favicon and tile tags. To be an effective fe dev require tons of learning on the job and doing your research as new things arrive constantly, best practices change, and you will encounter many things you haven’t before. Like I said; experience and breadth of knowledge is an interesting indicator, but it doesn’t make much sense to me to have it as the main indicator. > Imagine the guy saying "I don't know, I never memorize this stuff". Then I would ask them to look it up and get an impression of their ability to gather quality knowledge and understanding. Not a problem to me, and I would appreciate the opportunity to gain insight in those skills.
- AdrianB1 5y ago
  > the ability to gather knowledge quickly, learn on the spot, so they can work on things they haven’t worked on before That is perfect for a junior, not acceptable for a senior that is supposed to already have solid experience with that stuff; HTML tags should be something they worked before a lot.

codeptualize 5y ago

How often do you write the html params and meta tags? I really don’t care if someone memorized all the meta tags. What matters to me is that if I ask them to write a template they can find out what they need to include according to the latest best practices and our situation. I rather have them looking it up than relying on something they memorized years ago and might be outdated. Looking things up is not the same as carelessly assembling as you describe it. It’s the ability to gather knowledge quickly, learn on the spot, so they can work on things they haven’t worked on before, and keep up with the latest best practices. Absolutely essential to FE development. And some of it is assembling and relying on tools to work efficiently; for example I would highly recommend to generate Favicon and tile tags. To be an effective fe dev require tons of learning on the job and doing your research as new things arrive constantly, best practices change, and you will encounter many things you haven’t before. Like I said; experience and breadth of knowledge is an interesting indicator, but it doesn’t make much sense to me to have it as the main indicator. > Imagine the guy saying "I don't know, I never memorize this stuff". Then I would ask them to look it up and get an impression of their ability to gather quality knowledge and understanding. Not a problem to me, and I would appreciate the opportunity to gain insight in those skills.

AdrianB1 5y ago
> the ability to gather knowledge quickly, learn on the spot, so they can work on things they haven’t worked on before That is perfect for a junior, not acceptable for a senior that is supposed to already have solid experience with that stuff; HTML tags should be something they worked before a lot.