Interview for a FRONT-END position -

Do you know what the scariest thing in the world is? Not knowing how to write a React component in a Ben Awad interview.

33:06 - you'd wrap fetchNextUser in a useCallback if you wanted to satisfy the linter and pass fetchNextUser to the dependency array. This is because the function is re-allocated on render because it's within render scope, and therefore the function reference changes between renders, causing your useEffect to every time (based on shallow comparison of the dep array), so useCallback avoids that and keeps the reference the same between renders.

0:50 Make a counter

I'd love to see you guys continue this as a series, gradually increasing the difficulty!

I wish every tech interview was as friendly

i like the fact that clement is humble and admit that he doesn't know about the error upfront

gender: “female”

so i work for him and he works for you...? i may have to quit

Clément's confidence started to increase once he figured out that the bug was from line 31 instead of 32.

Ben is doing the sassy interviewer stereotype perfectly here.

thank you, that was so nice! as a junior I feel comforted seeing this type of interview, I could actually answer those questions without even typing the code. now it would be really cool to see something like this for junior+, middle, middle+ etc. levels!

useCallback instead of useRef - it memoizes the fetch function for ref equality, so the effect doesnt rerun on every render. UseCallback will mean that if you eventually do a refactor so the function does depend on some value inside the component, your compiler will yell at you until you include it as a dependency. Useref might solve the problem now, but it can hide future potential dependencies. Also, working with a ref is annoying, constantly looking up .current or forgetting to.

At 11:50

fetchNextUser() is a function that gets newly created on every render call since its defined inside the component.