Finding bugs and understanding what is really happening within code is a lostart. Only truly good programmers are able to emulate the processor in theirown mind (e.g. read the code and understand how it might work without goingto the trouble of running it). Adam Barr wonders how programmers aresupposed to build better programs if they do not know what is going on incode. The true pursuit of most software programmers is not creatingapplications from scratch; the reality of their day-to-day work is that theyusually have to deal with inherited code. This code, likely written by someoneelse, must be optimized, tweaked, and improved. Therefore, programmers whoare adept at reading, understanding, and improving code are in hot demand.These skills are drawn to the forefront with the help of this new book.This book is language-independent. The author borrows from his extensiveexperience at Microsoft Corporation and as an independent consultant to showhow programming skills can be honed by going through the exercise of findingthe bugs in existing code. By teaching programmers how to troubleshoot, it isthe author's belief that programmers will learn how to think like a programmer,and ultimately produce better software in a more timely fashion.
Kurzbeschreibung
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
Produktbeschreibungen
Synopsis
Finding bugs and understanding what is really happening within code is a lostart. Only truly good programmers are able to emulate the processor in theirown mind (e.g. read the code and understand how it might work without goingto the trouble of running it). Adam Barr wonders how programmers aresupposed to build better programs if they do not know what is going on incode. The true pursuit of most software programmers is not creatingapplications from scratch; the reality of their day-to-day work is that theyusually have to deal with inherited code. This code, likely written by someoneelse, must be optimized, tweaked, and improved. Therefore, programmers whoare adept at reading, understanding, and improving code are in hot demand.These skills are drawn to the forefront with the help of this new book.This book is language-independent. The author borrows from his extensiveexperience at Microsoft Corporation and as an independent consultant to showhow programming skills can be honed by going through the exercise of findingthe bugs in existing code.By teaching programmers how to troubleshoot, it isthe author's belief that programmers will learn how to think like a programmer,and ultimately produce better software in a more timely fashion.
Buchrückseite
50 exercises to help you find bugs faster -- with less aggravation!
Bug hunting is an art, and you need to be a master. Get Find the Bug, and you'll become one. Long-time Microsoft programmer Adam Barr presents 50 programs, each with exactly one bug. Your assignment: find it. As you do, Barr will teach you how to "think like your processor"... anticipating exactly how code will behave, even without running it. You'll learn better ways to read code, understand it -- and above all, improve it. Whether you're building new systems or maintaining someone else's, you'll find bugs earlier, faster, with less frustration... and write cleaner code to begin with.
- Presents "bugged" programs in C, Java, Python, Perl, and x86 assembly language, with carefully explained solutions
- Includes language overviews to help you debug all 50 examples, even if you don't know the language
- Shows how to look past the "surface" of code to uncover its hidden internal logic
- Offers practical guidance on analyzing programs, including specific inputs to test
- Presents a wide range of realistic bugs, with no phony "gotchas"
- Draws on the types of coding and debugging challenges Microsoft uses to interview new programmers
- An indispensable resource for working programmers, maintainers, testers, quality specialists, and everyone involved in code reviews
© Copyright Pearson Education. All rights reserved.
Eine digitale Version dieses Buchs im Kindle-Shop verkaufen
Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen.
Weitere Informationen
Kundenrezensionen
Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
3.6 von 5 Sternen
7 Rezensionen
16 von 19 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen
Going from language to language is of dubious benefit
30. März 2005
Von Charles Ashbacher
- Veröffentlicht auf Amazon.com
Format:Taschenbuch
While this book does something that I am in strongly in favor of, I don't agree with the approach. Barr presents a series of code segments that contain bugs and the reader is challenged to find the error(s). The bugs introduced into the code are fairly common, so finding them will be excellent practice for coders at all levels of experience. The segments of code are short, generally less than two pages, so finding the bugs does not require a great deal of searching.
The problem is that the programs are written in C, Python, Java, Perl and x86 assembly. If you are experienced in a particular language, then the bugs will probably not challenge you. However, if you are a novice in a language, the ten pages devoted to introducing the language will not be enough to get you up to speed. I have taught all of these languages and I found it difficult to shift from one language to another. The syntax differences between the languages are enough to confuse even people experienced in all of them. I am also unconvinced that finding bugs in a language you are not using and are unfamiliar with will make you a better programmer.
The general sequence of the bug presentations is:
*) A textual explanation of the problem.
*) The source code.
*) Suggestions of questions to consider.
*) Hints of operations to perform when stepping through the code.
*) Explanation of the bug(s).
Which is certainly a sound approach.
I dithered a bit when trying to settle on a ranking for this book, largely due to the multiple languages. In the end, I settled on three stars because I believe that if you go through this book, it is more likely that instead of doing a few things well, you will do many things poorly.
The problem is that the programs are written in C, Python, Java, Perl and x86 assembly. If you are experienced in a particular language, then the bugs will probably not challenge you. However, if you are a novice in a language, the ten pages devoted to introducing the language will not be enough to get you up to speed. I have taught all of these languages and I found it difficult to shift from one language to another. The syntax differences between the languages are enough to confuse even people experienced in all of them. I am also unconvinced that finding bugs in a language you are not using and are unfamiliar with will make you a better programmer.
The general sequence of the bug presentations is:
*) A textual explanation of the problem.
*) The source code.
*) Suggestions of questions to consider.
*) Hints of operations to perform when stepping through the code.
*) Explanation of the bug(s).
Which is certainly a sound approach.
I dithered a bit when trying to settle on a ranking for this book, largely due to the multiple languages. In the end, I settled on three stars because I believe that if you go through this book, it is more likely that instead of doing a few things well, you will do many things poorly.
13 von 15 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen
Great "out of the box" thinking...
1. November 2004
Von Thomas Duff
- Veröffentlicht auf Amazon.com
Format:Taschenbuch
If you're a programmer who has to look at code that others have written, you'll appreciate this book... Find The Bug by Adam Barr (Addison-Wesley).
Chapter list: Bug Classification; Tips on Walking Through Code; C; Python; Java; Perl; x86 Assembly Language; Classification of Bugs; Index of Bugs by Type; References; Index
This is a excellent text to help you improve your skills on reading code and mentally debugging it. There are 10 short program or routines for each of the five languages. Your goal is to walk through the code and figure out what is the hidden error in it. There are three or four suggestions if you need help thinking it through, a couple of direct hints to focus your thoughts, and a complete explanation at the end. Even though you may not be familiar with some of the languages, Barr gives you a basic coverage of the fundamentals at the beginning of the chapter so that you can see if you are able to spot the error. Add to all that some good information on how best to walk through code, and you end up with a book that should be part of every developer's training. If you're part of a development group that does code walkthroughs, this would be an excellent guide to help everyone become more effective during the process.
A good way to step outside your normal thought processes and improve your skills... good stuff.
Chapter list: Bug Classification; Tips on Walking Through Code; C; Python; Java; Perl; x86 Assembly Language; Classification of Bugs; Index of Bugs by Type; References; Index
This is a excellent text to help you improve your skills on reading code and mentally debugging it. There are 10 short program or routines for each of the five languages. Your goal is to walk through the code and figure out what is the hidden error in it. There are three or four suggestions if you need help thinking it through, a couple of direct hints to focus your thoughts, and a complete explanation at the end. Even though you may not be familiar with some of the languages, Barr gives you a basic coverage of the fundamentals at the beginning of the chapter so that you can see if you are able to spot the error. Add to all that some good information on how best to walk through code, and you end up with a book that should be part of every developer's training. If you're part of a development group that does code walkthroughs, this would be an excellent guide to help everyone become more effective during the process.
A good way to step outside your normal thought processes and improve your skills... good stuff.
8 von 9 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen
Great read!
2. November 2004
Von JC Cannon
- Veröffentlicht auf Amazon.com
Format:Taschenbuch
Adam Barr steps you through code analysis in a logical fashion, guiding you around some obvious and not so obvious pitfalls. His writing style makes it easy to understand his concepts. Adam's selection of languages benefits programmers of all backgrounds. I especially enjoyed looking through the Python examples. The language summary at the beginning of each chapter is a great idea to acquaint newcomers to a language. Experienced programmers as well as hobbyists will find great value in the examples. Not only will you become a better debugger, you will become a better programmer.
›
Gehen Sie zu Amazon.com, um alle 7 Rezensionen zu sehen
3.6 von 5 Sternen
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
Ähnliche Artikel finden
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
