↳
I completed the challenge as well as two of the 'bonus; categories. My submission was not visually stunning or refactored - but it should have passed. Less
↳
I had a similar experience with Twitch. Very biased when it comes to technology choices. Frankly, the hiring manager I was dealing with seemed rather inexperienced as a hiring manager. I recommend Twitch examine their hiring process if they're looking for the best talent. Less
↳
Me already asking myself if this is really serious... Writing code on a white board? Less
↳
It depends... what is the purpose? 200 is a hard limit, or are we expecting more element to be loaded? Where will the code be used? First viable product, refactoring or optimization? Do we already have a utility library, or this is a one-off case? Without context it would be easiest to write the for(i=0;i<200;i++)(//code) JS. Less
↳
In general, I'm not sure about the answer, since I never do that, since the IDE will always highlight the error and I will fix it. But I think in the first case "undefined" and in the second case "error". Less
↳
1. What will be the result? console.log(a); var a; Answer: you will get an error as you are trying to console a property before declaring it . 2. a; const a; Answer: here if you are declaring this "a" property in a component you will get error you are not defining type or initial value to it. second for "const a" you will also receive an error as, while declaring const you should pass a initial value to it. which can not be changed after that. Less
↳
I discussed the observations, and likely origin of the cause as client vs. backend. Completed the validation exercise with some bug fixes and optimizations. Worked through the logic problem with backend developer to arrive at a solution. Less
↳
(I would say always use arrow but he wanted other)
↳
I answered to all questions which I was asked.
↳
Generic answers to generic questions, nothing technical.