Muutke küpsiste eelistusi

E-raamat: Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems

  • Formaat: EPUB+DRM
  • Ilmumisaeg: 23-Sep-2002
  • Kirjastus: Amacom
  • Keel: eng
  • ISBN-13: 9780814426784
  • Formaat - EPUB+DRM
  • Hind: 16,56 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

When the pressure is on to resolve an elusive software or hardware glitch, whats needed is a cool head courtesy of a set of rules guaranteed to work on any system, in any circumstance.

Written in a frank but engaging style, this book provides simple, foolproof principles guaranteed to help find any bug quickly. Recognized tech expert and author David Agans changes the way you think about debugging, making those pesky problems suddenly much easier to find and fix.

Agans identifies nine simple, practical rules that are applicable to any software application or hardware system, which can help detect any bug, no matter how tricky or obscure. Illustrating the rules with real-life bug-detection war stories, Debugging shows you how to:





Understand the system: how perceiving the ""roadmap"" can hasten your journey Quit thinking and look: when hands-on investigation cant be avoided Isolate critical factors: why changing one element at a time can be an essential tool Keep an audit trail: how keeping a record of the debugging process can win the day

Whether the system or program youre working on has been designed wrong, built wrong, or used wrong, Debugging helps you think correctly about bugs, so the problems virtually reveal themselves.
Introduction
1(8)
How Can That Work?
2(1)
Isn't It Obvious?
2(1)
Anyone Can Use It
3(1)
It'll Debug Anything
4(1)
But It Won't Prevent, Certify, or Triage Anything
5(1)
More Than Just Troubleshooting
6(1)
A Word About War Stories
7(1)
Stay Tuned
8(1)
The Rules---Suitable for Framing
9(2)
Understand the System
11(14)
Read the Manual
13(2)
Read Everything, Cover to Cover
15(2)
Know What's Reasonable
17(1)
Know the Road Map
18(2)
Know Your Tools
20(1)
Look It Up
21(2)
Remember
23(2)
Understand the System
23(2)
Make It Fail
25(20)
Do It Again
28(1)
Start at the Beginning
29(1)
Stimulate the Failure
29(1)
Don't Simulate the Failure
30(3)
What If It's Intermittent?
33(2)
What if I've Tried Everything and It's Still Intermittent?
35(4)
A Hard Look at Bad Luck
35(2)
Lies, Damn Lies, and Statistics
37(1)
Did You Fix It, or Did You Get Lucky?
37(2)
``But That Can't Happen''
39(2)
Never Throw Away a Debugging Tool
41(1)
Remember
42(3)
Make It Fail
42(3)
Quit Thinking and Look
45(22)
See the Failure
50(2)
See the Details
52(3)
Now You See It, Now You Don't
55(1)
Instrument the System
55(8)
Design Instrumentation In
56(3)
Build Instrumentation In Later
59(1)
Don't Be Afraid to Dive In
60(1)
Add Instrumentation On
61(1)
Instrumentation in Daily Life
62(1)
The Heisenberg Uncertainty Principle
63(1)
Guess Only to Focus the Search
64(2)
Remember
66(1)
Quit Thinking and Look
66(1)
Divide and Conquer
67(16)
Narrow the Search
71(5)
In the Ballpark
74(1)
Which Side Are You On?
74(2)
Inject Easy-to-Spot Patterns
76(2)
Start with the Bad
78(1)
Fix the Bugs You Know About
79(1)
Fix the Noise First
80(1)
Remember
80(3)
Divide and Conquer
80(3)
Change One Thing at a Time
83(14)
Use a Rifle, Not a Shotgun
85(3)
Grab the Brass Bar with Both Hands
88(1)
Change One Test at a Time
89(1)
Compare with a Good One
90(2)
What Did You Change Since the Last Time It Worked?
92(3)
Remember
95(2)
Change One Thing at a Time
95(2)
Keep an Audit Trail
97(10)
Write Down What You Did, in What Order, and What Happene
99(2)
The Devil Is in the Details
101(2)
Correlate
103(1)
Audit Trails for Design Are Also Good for Testing
104(1)
The Shortest Pencil Is Longer Than the Longest Memory
105(1)
Remember
106(1)
Keep an Audit Trail
106(1)
Check the Plug
107(8)
Question Your Assumptions
109(2)
Don't Start at Square Three
111(1)
Test the Tool
111(3)
Remember
114(1)
Check the Plug
114(1)
Get a Fresh View
115(10)
Ask for Help
116(3)
A Breath of Fresh Insight
116(1)
Ask an Expert
117(1)
The Voice of Experience
117(2)
Where to Get Help
119(1)
Don't Be Proud
120(1)
Report Symptoms, Not Theories
121(2)
You Don't Have to Be Sure
122(1)
Remember
123(2)
Get a Fresh View
123(2)
If You Didn't Fix It, It Ain't Fixed
125(8)
Check That It's Really Fixed
127(1)
Check That It's Really Your Fix That Fixed It
127(1)
It Never Just Goes Away by Itself
128(1)
Fix the Cause
129(2)
Fix the Process
131(1)
Remember
132(1)
If You Didn't Fix It, It Ain't Fixed
132(1)
All the Rules in One Story
133(4)
Easy Exercises for the Reader
137(20)
A Light Vacuuming Job
137(3)
A Flock of Bugs
140(4)
A Loose Restriction
144(6)
The Jig Is Up
150(7)
The View from the Help Desk
157(14)
Help Desk Constraints
159(1)
The Rules, Help Desk Style
160(9)
Understand the System
160(2)
Make It Fail
162(1)
Quit Thinking and Look
163(1)
Divide and Conquer
164(1)
Change One Thing at a Time
165(1)
Keep an Audit Trail
166(1)
Check the Plug
167(1)
Get a Fresh View
167(1)
If You Didn't Fix It, It Ain't Fixed
168(1)
Remember
169(2)
The View from the Help Desk Is Murky
169(2)
The Bottom Line
171(6)
The Debugging Rules Web Site
171(1)
If You're an Engineer
172(1)
If You're a Manager
172(1)
If You're a Teacher
173(1)
Remember
174(3)
Index 177