Your SlideShare is downloading. ×
0
Debugging   9 indispensable rules
Debugging   9 indispensable rules
Debugging   9 indispensable rules
Debugging   9 indispensable rules
Debugging   9 indispensable rules
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Debugging 9 indispensable rules

279

Published on

Based on a book written by David. J. Agans, this presentation outlines the basic rules of debugging.

Based on a book written by David. J. Agans, this presentation outlines the basic rules of debugging.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
279
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Debugging:9 Indispensable Rules(Rules 1-3)- Mudabbir Warsi (ITCM Dev, CA Technologies)
  • 2. Understand the System“It is not so impossible, however, that a man should possess all knowledge which is likely to beuseful to him in his work, and this, I have endeavored in my case to do”. – Sherlock HolmesRead the manualRemember Murphy’s LawKnow what is reasonableKnow the lay of the landKnow your tools o Choose the right tools o Use the tool correctly o Interpret the results correctly o Understand the limitations of your tools Debugging: 9 indispensable rules. 07/07/2011 Copyright (c) 2011 CA. All rights reserved.
  • 3. Make it fail“There is nothing like first-hand evidence”. – Sherlock HolmesHow to make it fail? o Start at the beginning o No detail is insignificant o Stimulate the failure. Don’t simulate the failure o What if it’s intermittent? o What if it’s still intermittent?Why to make it fail? o Did you fix it, or Did you get lucky? o But “that” can’t happen! Debugging: 9 indispensable rules. 07/07/2011 Copyright (c) 2011 CA. All rights reserved.
  • 4. Quit thinking and look“It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts tosuit theories , instead of theories to suit facts”. – Sherlock HolmesSee the failureMy eyes are open….Now what? o Design Instrumentation in o Build Instrumentation in laterThe Heisenberg uncertainty principleGuess, but look before you fix Debugging: 9 indispensable rules. 07/07/2011 Copyright (c) 2011 CA. All rights reserved.
  • 5. Questions

×