31–40 of 152 posts
1st: A company asks those questions because they don’t know better. Someone is good at remembering stuff and does so. He gets the job.
2nd: A company asks those questions because they don’t know better. Someone is a good developer but fails at these questions – with no specific reason. He doesn’t get the job.
I really like this js question (whiteboarding): Implement function foo which takes an integer size, and returns an array of that size where each element in that array is a function that returns the index of that function in the array. Testcase: 42 === foo(1000)[42]() There are 3 different correct solutions. Discuss which solution is better, worse... etc (if they get there) (could probably be worded better, I'm not an…
Edit: A good Google seems to suggest using JSON.stringify and JSON.parse to copy the value.
Edit 2: But even that doesn't seem to work :(
Edit 3: Got it, using a generator function. Which makes sense. I guess I'm not an expert yet! :)
This looks like a giant list of trivia that has almost no bearing on the day-to-day effectiveness of the candidate. For example, I don't have the slightest clue what the answer is to probably half of these and a lot of my job is to write javascript that gets run millions to billions of times a day. The "code questions", by contrast, were all ridiculously easy. So, would it really matter if you are hiring someone who…
Earlier quoted context omitted.
>Flexbox is well past the point where you should be "playing around" with it. It's time to straight-up learn it, if not start using it in production. I dont think that is 100% true quite yet. IE9 for example is still quite popular, not to mention the bugs in modern browsers. http://philipwalton.com/articles/normalizing-cross-browser-f...
IE9's global share is 2.13% and 3.84% in the US. It's 2.38% for the sites I'm supporting. Here's the simple answer for supporting old IE: http://dowebsitesneedtolookexactlythesameineverybrowser.com/ But to be more precise, graceful degradation is the answer. I'm building an interface that needs to last for several years, and IE9 is circling the drain. I can't justify making too many decisions around browsers that wil…
But people should be more worried about how it looks on a mobile device, at least 50% of our clients traffic are from mobile devices now a days...
This looks like a giant list of trivia that has almost no bearing on the day-to-day effectiveness of the candidate. For example, I don't have the slightest clue what the answer is to probably half of these and a lot of my job is to write javascript that gets run millions to billions of times a day. The "code questions", by contrast, were all ridiculously easy. So, would it really matter if you are hiring someone who…
For example, bad questions:
* How is responsive design different from adaptive design? - there's no formal definition of either. While it might prompt a discussion, it will probably just make the interviewee feel nervous, when you should be trying to get them to relax.
* Why is it called a Ternary expression, what does the word "Ternary" indicate? That's an etymology question. It might be interesting, but it gives no indication as to whether the person is a good developer or not.
* Explain how this works in JavaScript If you can do that effectively, you should probably be presenting and writing books on JavaScript.
Good questions are about opening up a conversation with the person. Why do they want to be a front end developer in your company? What would they be like to work with? Are they looking to specialise in a particular area of front end development, do design + coding, or front end with back end?
* If you could master one technology this year, what would it be? - I read that question last time I saw this link, and have used it a couple of times. It's nice because it tells you where someone wants to be. Think about how you'd react to answers like PHP, NodeCopter or SVG.
* What excites or interests you about coding? - it's open ended. If the interview can only say "I dunno", that tells you they're either not very communicative or not very interested in front end development.
* What tools do you use to test your code's performance? - I have worked with fantastic front end developers who were able to twist CSS and JS into doing anything, but the performance of their code was awful. They opened it in a browser, if it worked, they signed it off and left it for somebody else to speed it up. Depending on the role, that might be perfect, or you might be looking for the exact opposite. Either way, it's a good way of having that conversation with a prospective developer about what their opinion is.
This looks like a giant list of trivia that has almost no bearing on the day-to-day effectiveness of the candidate. For example, I don't have the slightest clue what the answer is to probably half of these and a lot of my job is to write javascript that gets run millions to billions of times a day. The "code questions", by contrast, were all ridiculously easy. So, would it really matter if you are hiring someone who…
Call and apply are core concepts to writing good javascript. I would not hire someone (at least for any sort of senior role) that could not tell you exactly how both of them work. Many of the other things on this page are certainly "trivia" that could be addressed by google when they come up, but not those.
But the biggest issue is the disagreement with the body of knowledge that everyone should have. Even in the body of knowledge, there's disagreements about what bits of knowledge go to which categories (Is it nice-to-know, or need-to-know?)
It's really no wonder you see such a broad range of candidate skills and knowledge. The sub-fields of the programming field can't even decide what everyone ought to know at various levels of experience!
Lets imagine the two worst case scenarios here: 1st: A company asks those questions because they don’t know better. Someone is good at remembering stuff and does so. He gets the job. 2nd: A company asks those questions because they don’t know better. Someone is a good developer but fails at these questions – with no specific reason. He doesn’t get the job.
Earlier quoted context omitted.
>Flexbox is well past the point where you should be "playing around" with it. It's time to straight-up learn it, if not start using it in production. I dont think that is 100% true quite yet. IE9 for example is still quite popular, not to mention the bugs in modern browsers. http://philipwalton.com/articles/normalizing-cross-browser-f...
IE9's global share is 2.13% and 3.84% in the US. It's 2.38% for the sites I'm supporting. Here's the simple answer for supporting old IE: http://dowebsitesneedtolookexactlythesameineverybrowser.com/ But to be more precise, graceful degradation is the answer. I'm building an interface that needs to last for several years, and IE9 is circling the drain. I can't justify making too many decisions around browsers that wil…
Lets imagine the two worst case scenarios here: 1st: A company asks those questions because they don’t know better. Someone is good at remembering stuff and does so. He gets the job. 2nd: A company asks those questions because they don’t know better. Someone is a good developer but fails at these questions – with no specific reason. He doesn’t get the job.
While there's definitely a lot of useless trivia (worse, useless trivia from 5+ years ago that no longer applies at all) in this list, the good parts of these questions _are the job_. If you don't know how to answer the relevant questions in this list, you aren't a good developer. There is currently an explosion of "front end developers" who don't know anything at all beyond "here's where I put in the bootstrap class…
Earlier quoted context omitted.
IE9's global share is 2.13% and 3.84% in the US. It's 2.38% for the sites I'm supporting. Here's the simple answer for supporting old IE: http://dowebsitesneedtolookexactlythesameineverybrowser.com/ But to be more precise, graceful degradation is the answer. I'm building an interface that needs to last for several years, and IE9 is circling the drain. I can't justify making too many decisions around browsers that wil…
Depending on your industry, IE is still a major player. But people should be more worried about how it looks on a mobile device, at least 50% of our clients traffic are from mobile devices now a days...