EXTREMEZONE FORUM
WWW.EXTREMEZONE.3XFORUM.RO - WWW.TORENTZ.3XFORUM.RO- WWW.PETARDEARTIFICII.CABANOVA.COM http://www.facebook.com/petardeartificiidevanzare
|
Lista Forumurilor Pe Tematici
|
EXTREMEZONE FORUM | Reguli | Inregistrare | Login
POZE EXTREMEZONE FORUM
Nu sunteti logat.
|
Nou pe simpatie:
Profil ElizaElizaiubi
 | Femeie
23 ani
Satu Mare
cauta Barbat
23 - 53 ani |
|
|
sanraj
INCEPATOR
Inregistrat: acum 16 ani
Postari: 45
|
|
Library of Congress Control | ISBN 978-1-4020-5539-3 | Pages: 232 | English | PDF | Size: 3.25 MB | RAR-Commpressed : 1.68 MB | No Password
You Write Software; You have Bugs
Why You Need This Book
This is a book about analyzing and improving C and C++ programs, written by software developers for software developers.
In the course of our software development work we have often been called upon to support customers and coach colleagues on how to find bugs. They were aware of the topics they had been taught in school: object-orientation, code reviews, and black-box vs. white-box testing, but most had only superficial knowledge of debugging tools, and rather fuzzy ideas about when to use a particular approach and what to do if the debugging tools gave confusing or even wrong results. So, time and time again we found ourselves having to teach people how to track down bugs. It surprised us that it simply had not occurrred to a lot of programmers that debugging could be turned into a systematic approach. While a lot of steps in software development can be captured in a process, when it came to debugging, the accepted belief was that you not only needed deep insight into the code – you also needed a sudden burst of brilliance when it came to tracking down a bug.
Unfortunately, Richard Feynman’s method of “write down the problem; think very hard; write down the answer” is not the most efficient and successful approach to fixing software problems. Once we realized that we were continually writing down the same step-by-step rules, and explaining the operation and limitations of the same tools for every bug report, the idea was born to gather all of our practical experience, collect all of this advice, and turn it into the book you are now holding.We can now point to the book when someone is faced with yet another bug-finding task. We also believe that a book such as this on systematic debugging patterns will be an interesting addition to a programming class, or a class on problem solving in software. In the end, the reason is simple . . .
Software has bugs. Period. Unfortunately, it is true. Even the good old "hello, world" program, known to virtually every C and C++ programmer in the world, can be considered to be buggy.1 Developing software means having to deal with defects; old ones, new ones,
the ones you created yourself, and those that others have put in the code.
Download
Code:
http://www.ziddu.com/downloadfile/1938938/SpringerTheDevelopersGuidetoDebuggingAug2008.rar.html |
|
|
| pus acum 16 ani |
|
