React.JS Live Coding Challenge | Problem Solving with Turing

The fifth episode of "Problem Solving with Turing" takes a look at Turing's Live Coding Challenge. It helps React.JS developers understand the kind of problems they must look at before sitting for the technical interview and test. Join the live to ace coding challenges and crack technical interviews with ease.

Become a Turing software developer today.

[kleberaugus]

Usually, I don't understand anything spoken in English in movies, but I understood everything the Turing guy was saying. Cool!

[growwithsagar]

we want more such videos. its helping us a lot

[abenerh]

Amazing video ! It reinforces what I already know but I also learned quite some stuff. New subscriber here

[dzulfiqarzaky]

Why there is much hate in this comment section, I mean he can be working with another js library and forget about the syntax. And maybe he got a coldfeet during the interview, this is a live stream interview and a lot of people watching. I didnt know about others but i myself is really am an introvert. Its really hard to code when people sees me. Or during the live stream. It feels like joining a dungeon during a raid boss and got a debuff to lower intelligent by 30-40% from the boss aura😂
By the way i intend to join as a mid level developer, wish me luck😂

[thelaitas]

There's pretty much no difference between Interface and Type, decide with your team what's your preference and stick to it, be consistent. Although the only difference that does come to mind is Discriminated Unions which can only be implemented using Type if I'm not mistaken.

[fredteixeira]

can we google during the interview? Let's say, in case we need to build a regex pattern, or to implement a JS reducer. Many people won't remember the syntax, which is fair

[nguyenkhoi]

I wonder why he didn't use const when declare useState

[khalidrafi]

The solution is pretty good although when updating users he could have added the new users array to the previous users state like this

=> [...prevExistingUsers, { name: `${first} ${last}`, picture: thumbnail }]);*

so the array will be updated along with the old elements. Another thing he could have tried is to only fetch when the currentIndex gets changed. That way the array will only extend when he press "next" button. Finally if we clean up the next and previous function using previous index:

const handlePrevious = () => {
setCurrentIndex(prevIndex => Math.max(prevIndex - 1, 0));
}

const handleNext = () => {
setCurrentIndex(prevIndex => Math.min(prevIndex + 1, existingUsers.length - 1));
}


easy way to reduce the complexity of the code.

[diaguitounkara]

Any challenge for PHP Developers with Laravel Framework ?

[richardramirez]

I tried React test at Turing page, but it is about old React, I do not understand this

[abdulmuhaminrehman]

so the Turing test is taken live like that ??

[crazcoder]

Index is exceeded so user is not found with that index..

[emanuelacosta]

Amazing content guys, this was for a senior position right? Can you do one for a mid-level position? Thanks!

[rakeshchandradash]

Question: Why a interface not a type
Possible Answer: Because we can extend the interface, in future if we have to create a new user type (IAdminUser) whuch has same properties as IUser and some extra properties then we can extend IUser and create a new interface

[shafayet_hossain]

interface extends to another interface

[LutherDePapier]

This war nearly two years ago now, so we wouldn't do it this way today I feel. In Next.js, what I did in a project is I loaded the entire list in a server component, then I passed the list to a client component. In the client component I divised the list in smaller equal lists thanks to Lodash. And then I put the list in a useState that I would change to the next position by clicking Next and the previous by clicking Previous, making sure that the previous button is disabled if the position is 0 and the next button is disabled if the position equal list.length.
Now if the list was too big I would limit and offset my fetches, but in this case I don't think it would be necessary to fetch again and again at each click of the button. Fetching the whole list once may be slower, but then clicking on Next and Previous is instantaneous and doesn't require any loading.

[AniketYadav-nufb]

Anyone please explain me the currentIndex logic I didn't get what he did...???

[arvindhashok]

Hmm It's not a difficult interview.

[ThirdWorldUSA]

Wow, this was torturous to watch. Was this for a senior role? It should have politely ended within the first 10 minutes. No wonder the software industry is falling apart. Unwillingness to pay for decent talent === "great" product. Two such components within a codebase will turn that codebase into an unmaintainable trash heap.