Scribd
Upload
115K views1 page

Appraisal

The document outlines best practices for developing code, including writing readable and efficient code, using helper methods, avoiding hardcoding, committing code regularly, keeping components small and specific, reusing components, consolidating duplicate code, and following naming conventions. It also discusses defect management by prioritizing and addressing customer defects. For personal development, it recommends improving presentation skills and technical skills like learning React, Redux, and other technologies.

Uploaded by

Saurav Singh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
115K views1 page

Appraisal

The document outlines best practices for developing code, including writing readable and efficient code, using helper methods, avoiding hardcoding, committing code regularly, keeping components small and specific, reusing components, consolidating duplicate code, and following naming conventions. It also discusses defect management by prioritizing and addressing customer defects. For personal development, it recommends improving presentation skills and technical skills like learning React, Redux, and other technologies.

Uploaded by

Saurav Singh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Develop Code

Adherence to standards in developing code


Adherence to internal TCS/client specified processes/systems thereby providing zero
defect delivery
1. Wrote readable yet efficient code.

2. Used helper methods to keep code concise and succinct.

3. Avoided any hard-coding other than constants

4. Saved and Committed code to bitbucket on regular basis to prevent any loss and have better
collaboration with team.

5. Kept components small and function-specific.

6. Created reusable components to keep creation of new components to the minimum required.

7. Consolidated duplicate code.

8. Named the components after the function that it performs.

9. Used PascalCase for components names.

10. Followed BEM convention for naming CSS classes.

11. Kept all the files related to any one component in single folder.

12. Used camelCase for helper or non-component files.

13.Used linter to help write clean, consistent and make code easier to review.

Defect Management
Closure of post implementation defects raised by customer within prescribed SLA

Defects raised by customer were handled on priority and suggested ideas were listed down and
implemented in subsequent reviews/release.

Personal Development
Kindly work on presentation skills and technical orientation towards better
productivity
Worked on improving my presentation skills by actively getting involved in requirement gathering phase,
technology selection followed by implementing those requirements and presenting/demonstrating them to
the customer. Upskiled my technical proficiency by learning relevant technologies like React, Redux, Docker,
NoSql, Html, CSS, Javascript, i18n, etc. to meet project technical requirements.

You might also like