Skip to content

Instantly share code, notes, and snippets.

@ninadvadujkar

ninadvadujkar/guidelines.md

Last active June 10, 2021 10:00
Show Gist options
  • Save ninadvadujkar/0de20e73b4a26d4f0b0911b1c0501c13 to your computer and use it in GitHub Desktop.
Save ninadvadujkar/0de20e73b4a26d4f0b0911b1c0501c13 to your computer and use it in GitHub Desktop.
Download ZIP
Guidelines for HCL Hands-on Test
Raw
guidelines.md

Guidelines

General Guidelines

  • Write appropriate unit tests for your code. Try to cover 100% of your code. Write tests for positive as well negative outcomes. Take edge cases into account.
  • If the problem is in Typescript, use default and custom types diligently. Please do not use any type. We care about type safety and you should too.
  • Make sure your code is well written and follows proper coding conventions.
    • Add useful comments wherever required
    • Lint your code
    • Use user-friendly, readable variable names etc.
  • Follow the guidelines/notes mentioned in the problem statement. For e.g. if we ask you to implement a form using Reactive Forms then please don't use ngModel.
  • Try to solve the problem with the most optimal solution (i.e. keep memory and time complexity into account when building a solution).

Note: Please note that we expect a maintainable, well written, well documented and well tested code that follows all best practices. We do not want a code that just "works".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment