Debugging tips for New software engineers
I feel Debugging is the toughest part of the software profession. One will have to spend lots of hours breaking the head to trace these bugs. At the same time, the satisfaction that we get when a bug is solved has no limit.
Now with some exprience in the field of software developement, I wanted to share some my learninings with the new software engineers. This isn't going to be a professional detailed procedure for the Debugging process. These are just the things that needs to be done before debugging an unexpected behaviour.
# 1 : Understand the code.
This is the most important tip for the best debugging process. Only when you clearly know what is happening at the base level, you ll be able to trace the cause of the problem. As far as possible avoid BLINDLY copying the code. I m not against reusing the codes, I stress not to use the codes without understanding what its functionlity and dependency.
# 2 : Do not panic.
I see many people get tensed when a bug is found in their code. Bugs aren't bane, infact they are one of the beauties of this field. Everyone puts bug - hence do not panic when there is a bug in the code you had written.
Now with some exprience in the field of software developement, I wanted to share some my learninings with the new software engineers. This isn't going to be a professional detailed procedure for the Debugging process. These are just the things that needs to be done before debugging an unexpected behaviour.
# 1 : Understand the code.
This is the most important tip for the best debugging process. Only when you clearly know what is happening at the base level, you ll be able to trace the cause of the problem. As far as possible avoid BLINDLY copying the code. I m not against reusing the codes, I stress not to use the codes without understanding what its functionlity and dependency.
# 2 : Do not panic.
I see many people get tensed when a bug is found in their code. Bugs aren't bane, infact they are one of the beauties of this field. Everyone puts bug - hence do not panic when there is a bug in the code you had written.
Be happy that the bug had come out at an earlier stage. When it is solved, the users will not be facing the problem again. Always take it as a learning oppurtunity and see to that such things never happen again.
# 3 : Prioritise the complexity and time availability.
This is another important decision to be taken. Carefully analyze the bug and prioritise the bug. Lets have two basic level for this:
Type 1 - Bug to be solved immediately,
Type 2 - Bug that can be solved slowly, i,e. Not an urgent issue and time can be taken for solving the problem.
# 4 : Do Not run for help Immediately.
Yes I really mean this. This is the most common mistake we do very often. When there is a bug DO NOT approach the seniors immediately. One main reason is that this habbit will never make you learn in your own.
Software Engineering isn't a spoon-feeding profession. Your senior will not always be there to solve your bugs - hence it is very important to make attempt to stand in your own.
Hence whenever there is a problem, think, analyze and try to check if you could solve it in your own. Browse the discussion forums in the internet for help. Even if the problem isn't solved, this will make you learn new things related to your task.
#5 : Seek the seniors for Help at the right time.
Well this might be a little contradict to the previous one. If the bug is to be solved immediately, you may spend 15-30 mins (say apprx. 1 hour for type 2 bug) to check if you could solve it in your own. If it takes more time, then approach the seniors for help immediately. Their experi ence will help you or they might redirect you to the right source.
Whats more interesting here is, sometimes while explaining the problem to others, you yourself might get the resolution flashing in you mind. [;-)]
#6 : Discuss with the senior engineers.
This is more important if you had solved the problem in your own. Tell the senior about the problem and the solution you had applied. Sometimes he might have a better solution than the one you had applied. If his is a better one, do not worry about the efforts you had put. A discarded effort is always better learning than the unattempted efforts.
After all life is a learning process. Isn't it? [;-)]
This is another important decision to be taken. Carefully analyze the bug and prioritise the bug. Lets have two basic level for this:
Type 1 - Bug to be solved immediately,
Type 2 - Bug that can be solved slowly, i,e. Not an urgent issue and time can be taken for solving the problem.
# 4 : Do Not run for help Immediately.
Yes I really mean this. This is the most common mistake we do very often. When there is a bug DO NOT approach the seniors immediately. One main reason is that this habbit will never make you learn in your own.
Software Engineering isn't a spoon-feeding profession. Your senior will not always be there to solve your bugs - hence it is very important to make attempt to stand in your own.
Hence whenever there is a problem, think, analyze and try to check if you could solve it in your own. Browse the discussion forums in the internet for help. Even if the problem isn't solved, this will make you learn new things related to your task.
#5 : Seek the seniors for Help at the right time.
Well this might be a little contradict to the previous one. If the bug is to be solved immediately, you may spend 15-30 mins (say apprx. 1 hour for type 2 bug) to check if you could solve it in your own. If it takes more time, then approach the seniors for help immediately. Their experi ence will help you or they might redirect you to the right source.
Whats more interesting here is, sometimes while explaining the problem to others, you yourself might get the resolution flashing in you mind. [;-)]
#6 : Discuss with the senior engineers.
This is more important if you had solved the problem in your own. Tell the senior about the problem and the solution you had applied. Sometimes he might have a better solution than the one you had applied. If his is a better one, do not worry about the efforts you had put. A discarded effort is always better learning than the unattempted efforts.
After all life is a learning process. Isn't it? [;-)]
Labels: debugging, software engineering
posted by Prathees R at 2:49 AM
4 Comments:
Nice one da.
Good one yar
Really worthy n great information .. really debugging is to difficult task in some scenarios..
Good one! esp. #4. You can move it to #1 or #2.
Post a Comment
<< Home