Code
For both frontend/backend:
- we prefer using:
- our own util functions (if available)
- battle-tested good libraries (with decisions)
- compiler and linter should be without any warnings or errors
- keep code stupid (debugging is twice as hard as coding)
- names should be describing well what they are for and adhere to our glossary
- avoid magic numbers, prefer to use named constant instead
- avoid obviously inefficient code if more efficient solutions are available (please benchmark or ask in case of doubt)
- Make sure the correct encoding (UTF-8) and line break type (LF) is used. This is probably not an issue when working with Linux but in Windows the defaults seem to be UTF-16 and CRLF so be aware when using different operating systems.
For frontend:
- don't overuse useEffect (see You Might Not Need an Effect)
- for longer strings like classNames template literals are preferred