วีดีโอ

What are the hot keys for the drawing pad?Where to find them?

I had terrible interview the other day for a junior role. Interviewer was rolling eyes, yawned once and asked the most generic and pointless questions, asked only one question about tech the rest were "give me example of X or Y in your current role, half of which didn't pertain to my current role. Lovely experience.

This was painful to watch. Realtime coding interviews do not realistically reflect an engineer's ability to assess a problem and solve it using all of the tools at their disposal. In this case, having a candidate draw out their logic and write code or pseudo code on a real whiteboard and then explain what they drew and wrote would have been more effective. Alternatively, giving the candidate a larger take home project that closely reflected the level of sophistication they need to have for the role, followed by a code review interview, would have been even better, as it would 1) demonstrate the ability to arrive at a working solution without hand-holding, 2) give the interviewer a good understanding of the candidate's communication skills, how the candidate approached the problem, why they implemented it in the way they did and whether they understood the code they wrote, and 3) would realistically reflect how they will interact with the team during PR reviews. The interviewer in this mock interview had A LOT of patience; however, since filter() was suggested, I'm not sure why a simpler and more concise solution was not recommended for the initial problem. JavaScript is not my strength, but given the clue about using filter(), even I could see that no for loop was required and it could be made easier to read. For example: function diffSet(arr1, arr2) { let set1 = new Set(arr1); return arr2.filter(value => !set1.has(value)); } const array1 = [1, 2, 3, 4]; const array2 = [1, 2, 3, 4, 5]; console.log(diffSet(array1, array2)); // Output: [5] or if OOP needs to be demonstrated: class ArrayDiffer { constructor(arr1, arr2) { this.set1 = new Set(arr1); this.arr2 = arr2; } diffSet() { return this.arr2.filter(value => !this.set1.has(value)); } } const array1 = [1, 2, 3, 4]; const array2 = [1, 2, 3, 4, 5]; console.log(new ArrayDiffer(array1, array2).diffSet()); // Output: [5]

Thank you! Hope i nail my interview

Where is the delete tool?

Thanks for a great discussion. My input on the question of whether you should use AI to compare candidate's answers to an interview question is No. You should not compare candidates to other candidates. All candidates responses should be compared to the requirements for the role. Whether using AI or not, it is key to assess candidates based on job requirements, not against each other.

I hate to say this, but you guys are going about coding the wrong way. You are getting lost in the implementation details. The first thing to do is to draw pictures. This enables you properly visualize and understand the problem -- you did this when you had the lists side-by-side vertically. Afterwards you can choose your algorithms. At that point you can opt for using inbuilt functions like filter, include, splice etc. In this case, the problem is isolating the differences in both lists. The solution is iterating through the first list and for each member checking to ensure it is not in the second list. If it isn't push or append it to a temporary list. If it is in the second list delete it from the second list. When you have looped through the first list, concatenate your temporary list with whatever is left (if any) in the second list - those are items in the second list that do not exist in the first. Deleting the items in both lists enables us to ultimately determine the items in the second list not in the first. It also makes the code more efficient because the second list potentially gets smaller as we progress in the loop. The advantage of using the so-called old way is that it's simpler to do a runtime analysis of your code. When you use inbuilt functions, you have to be either knowledgeable of their implementation or view their documentations. In certain cases, they make your code more difficult to read and maintain. 😊

Nocmts

thanks

Why did this show in my recommendations?

Interviewer: "Which one do you want to start off with?" Interviewee: "Probably the array one." Interviewer: "Okay, sure." *picks the Diff one*

My brother in christ. The humiliation, the carnage. This was like watching a train wreck that lasts an hour looool. Had no idea this was online until someone messaged me about it ha. Everyone, everyone, I suck A LITTLE LESS now okay 🙂, I'm still dogsh*t but we still out here practicing don't worry. -guy in video

I love how patient the interviewer is.

I love to see this. Gives me more perspective

Great video guys ✌️