We try to keep our books accurate, but sometimes mistakes creep in. This page lists the errors submitted by our astute readers. If you've found a new error, please submit it.

The latest version of the book is P1.0, released over 2 years ago. If you've bought a PDF of the book and would like to upgrade it to this version (for free), visit your home page.

Key: Typo Tech. Error Suggestion Not a problem Next edition

By default this page displays the errata for the latest version of the book. If you have a previous version, select it here:  

(To find out what version you have, look at the copyright page, a few pages in from the front of the book. If it says (say) 'Second Printing', then here it'll be P2.0. If there are interim PDF releases in that printing, they'll be 2.1, 2.2, and so on.)

PDF Paper Description Found in Fixed in
19

#45667: Usage of the phrase "by and large" on pages 19 (twice!), 48, 49, and 72 is distracting. This reader suggests a simpler word such as "generally."--al anway

 P1.0
20-Nov-10
21

#47178: Those of us who have know that ignorance ... Suggestion: Change "know" to "known".--Dr. Alexander

 P1.0
12-Jun-11
23

#45656: By ensuring that your solution==>s<== fit==>s<== your group, you remove pain points, or uncomfortable bunching.--al anway

 P1.0
20-Nov-10
56
#45657: An expert ==>that<== isn’t growing isn’t an expert, because growing is what makes you an expert. (shouldn't people be referred to as "who" eve...more...
 P1.0
20-Nov-10
56

#45658: Every tool or technique has its limit. Every==>(need a space here)<==one has a task or a category of tasks it does not handle well.--al anway

 P1.0
20-Nov-10
58

#45659: Answering with a confident, knowledgeable response goes a long way to ==>shutting them down.<== (is this the desired implication? Please elaborate.)--al anway

 P1.0
20-Nov-10
59
#45660: Being able to go deeper than the Cynics will allow you ==>shut them down.<== (same issue as above, plus a typo if this wording is intended: "t...more...
 P1.0
20-Nov-10
59

#45661: People will dig their ==>heals<== in if they feel they are being attacked or unfairly criticized.--al anway

 P1.0
20-Nov-10
60
#45662: At first glance it would seem ==>to not affect<== other people, because you write unit tests to work with your own code. (word order improveme...more...
 P1.0
20-Nov-10
61

#45663: Jump onto the public forums for the tool you==>r<== are trying ==><== push.--al anway

 P1.0
20-Nov-10
70

#45664: Two uses of "brown-bag session" on the same page: the content seems redundant around both references.--al anway

 P1.0
20-Nov-10
71
#45666: There are a number of ways, but one that ==>jumps to mind<== occurred while I was writing this book. I have logo stickers for the software pro...more...
 P1.0
20-Nov-10
79

#47179: Page 79, 4th paragraph: Also, MySQL had just had just passed ...Suggestion: Remove one time "had just"--Dr. Alexander

 P1.0
12-Jun-11
79

#45668: Also, MySQL ==>had just had just<== passed to a new owner--al anway

 P1.0
20-Nov-10
81 I’d m

#45669: I’d make the argument that you should be doing these things anyway, but to each ==>their<== own. ("his" / "his/her" / etc.)--al anway

 P1.0
20-Nov-10
83

#45670: "==>Even if they are,<== most people have to be confronted to own their mistakes." (This is unclear.)--al anway

 P1.0
20-Nov-10
83
#45671: Any perception of ==>dishonestly<== will immediately cause them to clam up. (also, "clam up": is that what is meant? They won't object to the ...more...
 P1.0
20-Nov-10
86

#45672: There’s a meme that ==>come<== from the Bible--al anway

 P1.0
20-Nov-10
86

#45673: It allows you to get noticed by people who are trying to solve similar problems ==>(to the ones)<== you are trying to solve.--al anway

 P1.0
20-Nov-10
88

#45674: They may make ==>that<== criteria public, or they might not. ("those" or "the")--al anway

 P1.0
20-Nov-10
95

#45675: It is a pretty typical MVC framework that integrated with a couple ==>(of)<== other buzzword frameworks (dependency injection and ORM).--al anway

 P1.0
20-Nov-10
97

#46425: test-driven development should be TDD not TTD.--Markus Tenghall

 P1.0
20-Feb-11
97
#45676: However, if your organization has problems with bug==>s<== fixes frequently conflicting with each other, you have a good case for unit testing...more...
 P1.0
20-Nov-10
101

#45677: Rupesh wanted to get his web==>(hyphen, not space)<==developing co-workers onto Eclipse.--al anway

 P1.0
20-Nov-10
101

#45678: He wanted to make ==>is<== easier to push source control, build scripts, and continuous integration further down the line.--al anway

 P1.0
20-Nov-10
102

#47180: Page 102, 3rd sentence in 21.2: one of the small repeating joke is the TPS report. Suggestion: Change "joke" to "jokes"--Dr. Alexander

 P1.0
12-Jun-11
102
#45679: It works because you use people’s own desires ==>against them<==. (This reader doesn't believe the statement. You're using their desires to a...more...
 P1.0
20-Nov-10
102

#45680: In the movie Office Space, one of the small repeating joke==><== is the TPS report.--al anway

 P1.0
20-Nov-10
103
#45681: There’s a big difference between "I have this great thing...just so you know, you have to use x to take advantage of it." and "Before I get st...more...
 P1.0
20-Nov-10
104
#45682: As always, you have to make sure you aren’t attacking the Burned, but ==>you have proof that they can get back up on the horse.<== (This reade...more...
 P1.0
20-Nov-10
104

#45683: If that happens, you have ==>(a)<==cool solution that doesn’t help you with your goal.--al anway

 P1.0
20-Nov-10
107

#45684: They become advocates, and you continue to the next ==>most easy<== group and repeat. ("easiest"? "most skeptical"?)--al anway

 P1.0
20-Nov-10
109

#45685: Not including people, even the Irrational, in your efforts might seem a bit passive==>(hyphen, not space)<==aggressive.--al anway

 P1.0
20-Nov-10
109
#45686: You’ll have to demonstrate that whatever irrational, maybe even impossible==>(,)<== problem they have is not relevant to the professional deve...more...
 P1.0
20-Nov-10
110
#45687: Therefore, the key is to avoid them as one would a pit of spikes, instead of seeking to beat them in a bare-knuckled fight to the death. (Inco...more...
 P1.0
20-Nov-10
113

#45688: Add to it that there isn’t ==>(just)<== one thing that will convert them.--al anway

 P1.0
20-Nov-10
114
#46411: The last sentence of the first paragraph uses "hard" where it means "hardest", and has an awkward comma. Change it to read, "But you should no...more...
 P1.0
17-Feb-11
114

#45689: But you cannot approach the hard group==>,<== until you at least have some converts on your side. (and italicize "some"?)--al anway

 P1.0
20-Nov-10
114
#45690: If you cannot convince co-workers who are ostensibly your peers to come over, why should the Boss? And ==>they’re<== not wrong to have that at...more...
 P1.0
20-Nov-10
115
#45691: If you want them to actively participate in the effort or even if you are merely repeating any opinions they have expressed, you ==>have to<==...more...
 P1.0
20-Nov-10
118
#45692: One person can be easily dismissed, but with each person ==>that ("who")<== repeats your message, it becomes harder ==>(for the listener)<== t...more...
 P1.0
20-Nov-10
119

#45693: You can’t always convince everyone, and you sure==>(ly)<== can’t convince the Irrational. (or "you rarely can"?)--al anway

 P1.0
20-Nov-10
123
#45694: I had pushed frameworks, code generation, and unit testing ==>to no mostly no ("mostly to no")<== avail. I had heard pretty much the same old ...more...
 P1.0
20-Nov-10
126

#47181: Page 126, in "You Don't Always Reap the Rewards": unit testing to no mostly no avail. Suggestion: remove "no" before mostly.--Dr. Alexander

 P1.0
12-Jun-11