> How do you implement Server Side Rendering or SSR?
Easy, you don't. Don't look up guides, don't try to figure it out yourself, there are so many gotchas that you will never be successful. React on the server is horrible. Yes, even in Next. Don't do it.
> How do you enable production mode in React?
This isn't a React question, it's a bundler question, which is something you do once per project and never touch again until it breaks. Why are we asking this?
"In practical terms, what makes unit testing a React component different from unit testing a vanilla JS function or class?"
"Give an example of an app or site where SSR would be a great idea, an an example where it would be a horrible idea. For each, explain why."
"When adding dependencies to a useEffect call, what are the pros and cons of passing in an object versus passing in decomposed fields from that object?"
@twipped If the candidate can screen share, I love to do: "Pick an Open Source library you use regularly. Let's go find the source or API docs. Show me one thing you think is really clever about the library or its API. And what's one thing about it that you always forget or misremember or think is klunky?"
@rick I've come up with a code review trial. It's a basic tabs switcher composed of two components. There's a little bit of advanced react engineering in it, in the way I've used the Children toolset.
The code works, but I have deliberately written it badly, there's just a TON of really bad practices in it and ways it can break super easily. I'm gonna ask him to point out what's wrong, and fix it.
@rick A few years ago I'd have agreed with that, I used to do a ton of tooling to enable css modules so that I didn't have to do css-in-js, but I've come to actually really like Emotion in the last two years. It's very powerful.
Add comment