react-error-boundary VS naming-cheatsheet

I use the use-error-boundary module for this just to never have to write a class component myself!

Requires a dependency but you can absolutely use error boundaries with functional components via react-error-boundary: https://github.com/bvaughn/react-error-boundary

as for checking errors: https://github.com/bvaughn/react-error-boundary

For those of you, who hate re-inventing the wheel or just prefer libraries for already solved problems, there is a nice one that implements a flexible ErrorBoundary component and has a few useful utils similar to those described above: GitHub - bvaughn/react-error-boundary

Use https://github.com/bvaughn/react-error-boundary for error boundaries and you won't have to write one yourself.

There's no reason to manually write an error boundary as a class component yourself, either, given that https://github.com/bvaughn/react-error-boundary exists.

Yeah, and even in that case, you should probably be using https://github.com/bvaughn/react-error-boundary rather than writing your own from scratch.

they can https://github.com/bvaughn/react-error-boundary (this is from the react team) doesn't matter how it works internally, im not going to write a class just for error handling.

i would not bother with classes tbh, use this: https://github.com/bvaughn/react-error-boundary it's made by a react core team member and they even recommend it.

This guide is my go-to recommendation for freshers for "naming things": https://github.com/kettanaito/naming-cheatsheet

Use better naming. What's variablename? var iab; len(name)? What does reader do? Read a book? https://github.com/kettanaito/naming-cheatsheet

Not an answer, but https://github.com/kettanaito/naming-cheatsheet

But why would you need variable inside a function with the same name? https://github.com/kettanaito/naming-cheatsheet

Use the programming language you're most comfortable with if requirements are not strictly coupled to one programming language. Share your thoughts while you're coding so the interviewers can feel your way of thinking and problem-solving. Also, ask questions when something needs to be clarified for you. Try not to write pieces of code you don't fully understand, for example, using IIFE and not knowing how to pass an argument into it, using ; in front of it, and not knowing why it's used. Try to write readable code with understandable variable and function names. Avoid writing too nested statements, so it's not easy to understand the code's flow. Try to write code that is easy to cover with the tests.

Naming Convention Cheatsheet

Enforce style with a linter. In the js world there is also prettier. Agree upon a naming style for instance this naming cheatsheet although that is harder to enforce

What a great answer :)

Regarding naming things, this comes to my mind: https://github.com/kettanaito/naming-cheatsheet