Errata

Head First Software Development

Errata for Head First Software Development

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page ...
."

Small typo: "[...] what your software needed to do [...]."

 Anonymous   
Printed Page 13 - 4
/ 0.8 = 11

Anonymous   
Printed Page 13 - 4
/ 0.8 x 1/70% = 16

Anonymous   
Printed Page 40
bottom right

in the "There are no dumb questions" for the last Question we have a typo in the answer: "... at the beginning of the prject." is missing the vowel "o" -> project

 Elisei TATARU  Jan 20, 2020 
Printed Page 51
First paragraph, second sentence

Sentence: "So whenever planing poker..."
Should read: "So whenever planning poker..."

 Wes  Feb 08, 2009 
54
2

This typo is in the word "mont" in the following:
calendar mont

 Abder-Rahman  Jun 10, 2010 
64
Before the last paragraph

Error in the SECOND word "you", as it should be "your".

Or do you just ask the customer how long he thinks would work, forgetting about all your hard work to come up with "you" estimates in the first place?

 Abder-Rahman  Jun 11, 2010 
77
In the Brain Power Box at the end right of the page

Some of the letters of the "Brain Power" box are mixed together.

 Abder-Rahman  Jun 11, 2010 
Printed Page 78
Second question at bottom

Answer to question "How did you come up with 190 days" mentions the usage of "Team Velocity", when in fact the estimate of 190 is in workable days, with an assumed velocity of 1.0. The velocity of 0.7 is applied later.

 Wes  Feb 08, 2009 
80
"Dumb Questions", right column

"10, 20, 30, 40, and 50" are *multiples* of ten, not "powers of ten". Powers of ten are 10, 100, 1000, 10000, etc.

 Anonymous  Feb 06, 2010 
Printed Page 82
Thirs Milestone paragraph

Comma in beginning of 4th line should instead be at end of 3rd line

 Wes  Feb 08, 2009 
Printed Page 92
Picture

Head/hairline is obviously clipped by hidden formatting box or bounding rectangle

 Wes  Feb 08, 2009 
Printed Page 105
Answer to 18 across

Not sure where the answer to this 18 across question is in the text. Is this supposed to be surmised from the graph on page 77?

 Wes  Feb 08, 2009 
Printed Page 112
1st paragraph of text (not the bubble)

It says: "Your user stories were for your users; they helped describe exactly what you software needed to do

Anonymous   
112
2nd paragraph

Typo in "you", as it should be "your"

Your user stories were for your user; they helped describe exactly what "you" software......

 Abder-Rahman  Jun 12, 2010 
114
Last paragraph second column

To avoid these problem,.....

 Abder-Rahman  Jun 12, 2010 
Printed Page 156
Heading

typo: "responsibilies" -> "responsibilities"

 Anonymous   
Printed Page 158
Note on the right

typo: "responsibilty" -> "responsibility"

 Anonymous   
Printed Page 159
Heading

typo: "responsibilies" -> "responsibilities"

 Anonymous   
Printed Page 173
The first sentence of "Down"

It says: "Unplanned tasks are treated the [same] as unplanned tasks once they are on your board."

Must say: "Unplanned tasks are treated the [same] as planned tasks once they are on your board."

 Anonymous   
Printed Page 232
In the console picture

It says:

hfsd> svn add build.xml
A build2.xml

Must say:

hfsd> svn add build.xml
A build.xml

 Anonymous   
Printed Page 328
"Lots more communication" section

"..... and get to see the any note....."

The word "the" should be deleted.

 Nabeel  Feb 05, 2015 
Printed Page 342
United States

Point #2 "if one if the developers" should be "if one of the developers"

 Nabeel  Feb 09, 2015 
Printed Page 367
First "magnet" right on top

On p. 366 the method name is defined as "getOrdersThatMatchKeywords" but here it says "getOrdersThatMatchKeyword". The
same typo occurrs on p. 368 in the last magnet.

 Anonymous   
Printed Page 367
Bottom (the last method that is meant to complete)

The method "public String[] getAllOrdersForFlight(String flightNo) { ... }" should have a return type of "Order[]" not
"String[]" because getOrdersThatMatchKeywords() returns an "Order[]". For comparison, on p. 368 in the solution to this
example it is done right.

 Anonymous   
Printed Page 374
Top and middle

The source code of the exercise on this page is not the same as the source code of the solution on p. 376 to which it
refers:

After "private String qk = ..." there's missing "private MercuryMeals instance;" (as on p. 376).

The first implementation line of "public MercuryMeals getInstance()" should read "this.instance = new MercuryMeals();",
as on p. 376.

 Anonymous   
Printed Page 375
Middle

Within the submitOrder method there's a missing ending brace of the try-block so that the code wouldn't compile. There
must be a "}" right before the "catch" keyword.

Same on page 377.

 Anonymous   
Printed Page 393
First paragraph, last sentence.

Profanity. Ouch.

 Anonymous  Feb 14, 2013 
Printed Page 402
the bottom of the page

The calculation is incorrect:
0.8 x (13 - 4) = 7
should be:

 Anonymous   
Printed Page 402
second part of the page

In the second formula for calculating the number of days needed for fixing all the bugs, the authors have multiplied the number of the left bugs (13-4)by 0.8,as follows:

0.8 * (13-4) = 7 days

This is wrong. The correct action would be dividing of (13-4) by 0.8, as below:

(13-4) / 0.8 = 11.25 ,or 11 days

One other (bad) thing about this error is that the result of this calculation has been used in the next parts of the book, as well.

Mehraneh Shantiaei  Apr 23, 2011 
Printed Page 404
the bottom of the page

The calculation is incorrect:
0.8 x (13 - 4) x 1/70% = 10
should be:

 Anonymous   
Printed Page 406
the bottom of the page

Issue:
Task estimates to fix remaining bugs are incorrect.
Description:
According to the spike testing,
10 days (in fact, 16 days) is "working day" (time).
But, task estimates should be "person-day" (work).
So, it should be 10 x 3 (in fact, 16 x 3)
Problem:
If we correct this error, the iteration will need to be extended,
because the iteration need to finish {12 + 4 + (10x3)} days of work
(in fact, 12 + 4 + (16x3))

Anonymous   
Printed Page 441
4th paragraph

By now, you should know that violates the Single Responsibility Principle.
->
By now, you should know that [this?] violates the Single Responsibility Principle.

 Anonymous