Skip to content Skip to footer

Developer Training

All engineers,
When writing code just follow this basic guidelines:

  1. Give logical and easy to understand function, variables and class names (if they become long names it’s fine)
  2. ⁠any function should not be more than one screen in height.
  3. ⁠division of responsibility: do not overload any function or class with too many responsibilities. Always keep refactoring code to divide the responsibilities in classes and function, every class and function should have only one CLEAR and limited responsibility
  4. ⁠never eat errors – means don’t write empty catch statements. If there is error throw it or log it but don’t silently ignore it in code
  5. ⁠always check inputs are exactly what is expected. Instead of just assuming the input or parameter is correct json. Validate it first and throw errors. Just because it is called by our code doesn’t mean we will always have valid inputs to any api/functions

If you follow this basic rules, it’s enough for now. Advanced class design etc can be learned and incorporated later.

Topics to read for UI developers:

  1. OOP – SOLID principle
  2. “This” in Javascript
  • call (bind)
  1. Callback hell – Javascript
  2. Event Loop – Javascript
  3. Data Binding – Angular

SOLID OOP – for all devs
Separation of Concerns – another topic to read for everyone

Was This Article Helpful?


There are no comments yet

Leave a comment

Your email address will not be published. Required fields are marked *

Close Bitnami banner