Historical errata for Ship It!

This sidebar Dilbert on Deadlines

In the last paragraph, first sentence, after the semi-colon, you have, “we want find what works for us.” You are missing the word “to” between “want” and “find”.

In the acknowledgements section titled “From Jared”, second paragraph, first sentence, you have ,“… working on the The Book.”. The first “the” should be removed.

In the second paragraph, first sentence, you have, “you need a source code management (SCM) system system,”. The second “system” should be removed.

In the last bullet point under the “Am I Doing This Right?” section, you have, “Can you system notify …”. “you” should be “your”.

In the second paragraph, last sentence, you have, “so you can make changes to page very easily.”. You should add the word “a” between “to” and “page”.

In the sentence that is right below figure 3.3, you have, “the About dialog box would probably be considered be a fluff feature.”. The word “be” after the word “considered” should be removed.

In the second paragraph, second sentence, you have, “unless there’s good—and widely publicized—reason to …”. This should either be, “unless there’s good—and widely publicized—reasons to …”, note the plural “reasons”, or it should be, “unless there’s a good—and widely publicized—reason to …”, note the addition of the word “a” after “there’s”.

In the paragraph right before the section named “Tumbleweed Developers”, third sentence, you have, “but it’s starting point for his work.”. The word “a” should be inserted between “it’s” and “starting”.

In the second paragraph in the section named, “Team Communication”, the third sentence, you have, “when he ate alone …”. It should probably be, “which he ate alone …”.

In the “Patterns” box, first paragraph, last sentence, you have, “and allow you communicate clearly …”. Insert the word “to” between “you” and “communicate”.

In the first paragraph, fifth sentence, you have, “will make you look like a programming gods, …”. Either the word “gods” should be singular or the word “a” before the word “programming” should be removed. Probably “gods” should be singular. It reads better.

In the first sentence in the “Design Tricks” block you have, “The following are few …”. The word “a” should be inserted between “are” and “few”.

In the last paragraph, third sentence, you have, “that had an statistical algorithm in it”. The word “an” should be “a”.

In the line preceding the bullet points at the bottom of the page, you have, “To summarize, to the following:”. The second occurrence of the word “to” should be “do”.

In the last bullet point, the second to last sentence, you have, “The second is a too long-winded.”. The word “a” should be deleted.

In the paragraph after Tip 42, fourth sentence, you have, “you want find out why”. Insert the word “to” between “want” and “find”.

Tip 39 is the same as Tip 7. I didn’t notice this until I was reading the appendix. Maybe you should refer to Tip 7 in the place where you introduced Tip 39 on page 153.

In the description of Rake, second sentence, you have, “It also support such things”. The word “support” should be “supports”.

In the paragraph talking about general scripting languages, first sentence, you have, “general-purpose scripting languages gets pressed into action.”. The word “gets” should be “get”.

Duplicate tip appears here as well (see errata for pg 163)

“You can reign in a tumbleweed developer … ” should actually read “You can rein in a tumbleweed developer …”

Foot note reads: " … It means the tools is …"

It should be: “… It means that the tool is …”

“We hope our experience will keep you from making
the same mistakes we did” should read “the same mistakes we made”.

Third paragraph’s first sentence ends with “let alone a a CI system.” Drop the duplicated word.

Footnote #7 - Web address no longer live:
…www.pragmaticprogrammer.com/pa/pa.html

I would really suggest you include Perforce in your list of suggested SCM systems in Appendix B. I know you can’t include every SCM system out there, but considering the inclusion of SourceSafe and CVS, Perforce is at least as popular as these systems and way more current / actively maintained,

The screenshot on this page along with other pages are illegible for me due to their small size. Unless you are willing to devote more physical space to the screenshots, I suggest removing them and including more explanatory text instead.

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!

Well done article that. I’ll make sure to use it wseily.