Senior Frontend Developer Interview Questions 2024 

You have a problem with this becaus you are noob and you should learn JS exclusively for a year or two before even thinking about React or Frameworks. "Essential state" wording made perfect sense in the context of the conversation and the explanation, but there is no such thing.

I think it just means state that's the primary state, state that you cannot improve or "process" on the front end in a transformative way, it needs to be present in the state system verbatim. he gave the example of a shopping cart, the individual items names can't be "calculated" so those item cards are using "essential state". the shopping cart subtotal is "derived" from the essential state (a reducer pattern summing up all the cart items to a total). the subtotal isn't "essential" in that sense, you can't infer the items from a different piece of data in the global state. you need the original copy of the data. you CAN infer the subtotal as long as you have the list of items. including the subtotal in the larger global state isn't really necessary (unless you have other reasons to calculate and store this globally, whereas in a typical scenario you'd (probably, this is an example) just calculate it in the cart modal component as it receives the cart items from the server database, renders both the item cards and the subtotal, and passes the value down). it's not something you'd imagine would be repeated often or worth it to have calculated in the backend or wherever else the original cart data found itself born unto the world. it's situational, hence why these terms are "colloquial" and can't be found. If you're building a formal understanding, this guy essentially coined the term. tbf it is kinda a secret, one that he found through his direct experience of this kind of situation. he's a senior after all; few learn state management this intimately essential as in the literal sense, "essence of", not primarily the social sense, "urgent/important/critical". @MrZerosixZerooone hey don't be rude. React's easy to pick up. ending up on videos like this means they're looking for deep knowledge. they clearly are trying to learn. Dan Abramov didn't even learn flexbox for years upon years. you want him to sit in vscode doing hello world and algorithms in JS for two entire years? boring. he's studying web dev, let him learn web dev. he'll get there. give some people some slack, let them walk their path

Hey @rjborba, referencing the React Documentation: "Unlike PureComponent, memo does not compare the new and the old state. In function components, calling the set function with the same state already prevents re-renders by default, even without memo." React.memo and PureComponents are two very different things and in functional components, memoizations happens at many different levels by default so there is no need to use PureComponents. Referencing the docs, functional components are preferred with React.memo rather than PureComponets(class based). You can read more here: react.dev/reference/react/PureComponent#migrating-from-a-purecomponent-class-component-to-a-function

@@therealseniordev I’ve been trying to answer back but by comments keep vanishing. Maybe because I’m sharing an link to a implementation that exemplifies what I’m trying to say. But as it seems to be not possible, I’m going to explain myself here. First of all, I’m a big fan of your work. Thanks for these videos. They’re pretty helpful. About the pure components, it is unrelated to use state change. It is related to prevent the children to be rerendered when the parent is rerendered for changes in states that the children is not dependent of. So, essentially as it is today, pure components are components that has a MEMO call. Documentation is a bit misleading regarding that. They just stop the natural propagation of react rerender

@@rjborba You are conflating something key: a Pure Component is a specific React implementation for class components, which is different than how we talk about things like "pure functional components" today. So it is indeed related to state changes.

Best of success @iziversano

Move of those coming soon @onecurious

Glad you enjoyed it @nazardzys

Awesome @MeLu! glad to have you on the channel

Noted @Johan

You are welcome @cankat

Glad you found it useful @renato

You are welcome @chiran! Glad you enjoyed it :)

Thank you @anastasia

Yep, ive worked a bit with react but a lot you learn as you go and dont remember all the time, its crazy what the modern world has become

Do you understand that firing a person due to his low skillset is way harder than hiring? You cannot just trust them because they have some paper proving they're good. You do need to test people in some degree

we don't get to choose how we get interviewed, the only thing we can control is our preparation, is it fair? probably not. But is that world we live in. Win the game first, and change the game later when you get to the top.

@@grenadier4702 Why would you fire the developer for not having a certain skill? That is just wasteful, inefficient. Train the person on the job instead, make sure they get on top of your company tech stack. Teamwork. We are humans, we learn every day.

@@therealseniordev That might be true, but why would you agree to it? I have refused many companies because of their incompetent tests. Yet they continue like retarded zombies and don't listen to candidates....and eventually they are forced to hire consultants at triple rate to fix their shit.

thank you :)

Thanks @GreenWorld, glad you enjoyed it :)

You are welcome @nutan

glad it helped :)

this is a Frontend focused interview, not a JavaScript one, type coercion => TypeScript, Event Loop => JavaScript, Generator Functions => JavaScript, Inheritance => OOP & JS, we are pulling different series, this video is focused on more FE related questions, cheers

FrontEnd is so endless in technologies, names, paradigms, libraries, etc that it is virtually impossible to give one only type of interview. Depending on the role the company looks for they can be interested in architecture, patters, CSS and styles... Hundreds of possible combinations and limited time. One can not be answering, explaining, doing assigments etc forever

Thanks :)

yes, we had to move into that direction to give more value to the audience, is a mix of both, lecture and interviewing, hope it is helping you folks :)

@@therealseniordev Yes definitely really helpful. I was just trying to express the extent to which the candidate was experienced. 😅