By Developers, For Developers

Historical errata for Practices of an Agile Developer

PDF PgPaper PgTypeDescriptionFixed onComments
0TYPO

I might be making an invalid assumption here, but the current version of the book is listed as ‘P1.0 - April 6 2005’. I’m assuming that the 2005 is a typo that is supposed to read 2006.

Cheers

James
jeo30@cantab.net

2008-01-07
50TYPO

The rules above and below and the text “Strategic versus tactical design” are not outdented as on p.46 or p.52. The rules overlay some of the words of the first paragraph.

2008-01-07
29TYPO

The hyperlink to pragmaticprogrammer.com is relative (and thus points to file://…pragmaticprogrammer.com) rather than a fully qualified URL.

2008-01-07
34TYPO

Footnote 3 is lacking the infinitive “be”:

3This can still the case in some embedded systems development.

2008-01-07
33TYPO

Guitarist Pat Mathany should be “Metheny.”

2008-01-07
xTYPO

Page 131: “to track down problems in the middle of a entire” (should be “an entire”).
Page 106: “CofeeMaker” should be “CoffeeMaker”
Page 99: “No one have ever bothered” should be “No one has ever bothered”

Regards,

Glenn Miller

2008-01-07
146149TYPO

I have found half a dozen typos thus far in the book, so I decided I should probably start reporting them, since I’m one of those “word by word” readers!

Paragraph 3 starts “Effective collaborative is a …”, but it should probably say “Effective collaboration is a …”

2008-01-07
50TYPO

3rd paragraph from the top of page, statement: Consider the epic journey of Lewis and Clark3 across the United States
in 1804 Their

2008-01-07
2TYPO

The agilemanifesto.org link is relative, and tries to link to the site in the file directory (i.e. “C:/agilemanifesto.org”

2008-01-07
18TYPO

“his education any and will…”

should be (if I understood it correctly):

“his education in any way, and will…”

2008-01-07
135TYPO

on the first bullet point under Keeping Your Balance

I think you mean

- and eliminate -
and you have
- end eliminate -

2008-01-07
37TYPO

sentence says:
“when the pressure is on like that, you might feel intimidated and not want to question too deeply what you’ve been told too deeply.”

this says “too deeply” twice, and only needs to have it once in this sentence.

2008-01-07
103TYPO

The class “CoffeeMaker” is misspelled as “CofeeMaker” at one point.

2008-01-07
40OK

“Scrum protects the team from requirement changes during a
thirty-day sprint.”

What is Scrum? A quick Google search returns some Wikipedia pages about software development management and a Rugby news website. I can only assume we aren’t discussing Agile Rugby?

2009-01-20
99TYPO

Grammar mistake:

It seems the first step in using the system was to log on with their name and password, and the majority of the workers in this plant were illiterate. No one have ever bothered to ask them or get their feedback, so a completely useless system was installed. (have should be had)

2008-01-07
78TYPO

The link at the bottom is supposed to be www.xprogramming.com/software. That is, WITHOUT the .HTM

2011-07-29
50TYPO

The block quote on this page runs over the top of the text near it.

2011-07-29
tocTYPO

The table of contents in the epub edition has many ‘blank’ / ‘undefined’ entries.

When viewed in the Calibre ebook-reader (Ubuntu) they show up as blank lines.

When viewed with the sony prs-505 they show up as entries named ‘undefined’.

Strangely, the table of contents in the PDF edition seems to be fine!

2011-07-29
135TYPO

First bullet point, last sentence: “…can identify-end eliminate…” should be “…and eliminate”

2011-07-24
50ERROR

Horizontal bars on the “Strategic versus tactical design” heading are overlaying some words the first paragraph, lines 1 and 4.

2011-07-29
178TYPO

Software Project Management Practices: Failure versus Success
www.stsc.hill.af.mil/crosstalk/2004/10/0410Jones.html
Capers Jones analyzes the success and failure of 250 software projects.

Link is no good.

177TYPO

Damage Control
dev.buildpatterns.com/trac/wiki/DamageControl
A continuous integration tool written in Ruby on Rails.

Link is no good

176TYPO

Anthill
www.urbancode.com/projects/anthill/default.jsp
A tool that ensures a controlled build process (continuous integration) and promotes the sharing of knowledge within an organization.

link is no good

50TYPO

Bars above and below “trategy and tactical design” cut into text

63TYPO

The user should always to be able to remove an installation safely
and completely—especially in a QA environment.

Categories: