When you have a bug, what is the most important think you need to do before you solve it?

can you re-pro the bug? 

1. Re-produce the defect,

2. Assess the impact of the defect to the product, and set priority so that you decide whether to fix it urgently or can defer it (Defect triage process).

3. Investigate the reason causing the defect, and do a root cause analysis of the bug (Why and how the bug introduced, use root causes in team meetings to prevent future such instances)

4. Fix the defect, and do sufficient testing covering the areas might impact due to this change.

Check if changing it will affect the rest of the code in a bad way. For example, you have an error in a loop, first you have to check if removing or changing it may lead to an infinite loop.

-Replicate how to encounter the bug then do a root a cause analysis.

When I have is perhaps the first thing I need him and I care about is calm so that I think it's good and then I start to put my thoughts in the form of specific points and I start working on them.

There is one Rule.

Try to go into max9 steps deep. You identify bug, go back9 steps and I am sure you will get it resolved in3-4 steps.

• First Identify where error will be.
• Back track your code (max9 levels, you will find answer in3-4th level).

Believe me it works.

First and foremost you need to find out the damage caused so far due to the bug. what is the extent of damage it is causing. Is it very costing lot, then it is suppose to be the highest priority fix is required. if there is no impact on the business due to the bug, then the priority may be less. root cause and cost, impact analysis has to be carry out before fixing the bug based on the priority set to it.