Guidelines about exception handling and logging best practices

[sbimochan]

Best practices and few details and importance on Exception handling and Logging

Description

This is a language-agnostic guideline about Exception handling and Logging with examples on python and javascript

Motivation, Context and link to the ticket

There are multiple ways of making things work but would turn into confusions. I've tried to answer why we need it as well so that software engineers can reflect and go with the practice.

Related PRs

Link to related pull requests.: None

How Has This Been Tested?

• I ran in my local machine

Screenshots (if appropriate):

Type of change

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Update to existing guideline(s)
• New guideline(s)
• Miscellaneous change
• Docusaurus updates (new plugins, bug fix, etc.)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. Your team members are there to help!

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document (if applicable)
• I have added tests to cover my changes.
  • OR no tests update required.
• One or more required reviews requested.

[aws-amplify-ap-south-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-114.d223rc684oztgx.amplifyapp.com