Errata

Code Simplicity

Errata for Code Simplicity

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
PDF Page xi
Content Updates June 13, 2012

Spelling mistake/type: "necessary"
Quote
Eliminated a chapter that used to live between Chapters 1 and 2 which wasn?t necsesary to the content.
End Quote

 Paul  Jul 11, 2012 
PDF, Other Digital Version Page 7
5th bullet point

Since the author is describing "The Science of Software Development", it would be helpful if he made the distinction between a theory and an hypothesis with respect to the scientific method. A theory is a testable hypothesis supported by a preponderance of data. The author used the word "theory" in several places where the word "hypothesis" would be a better choice.

 Anonymous  Apr 02, 2012 
PDF, Other Digital Version Page 9
1st paragraph

The word "data" is the plural of the word "datum", so the phrase "when new data is discovered" could be reworded.

 Anonymous  Apr 02, 2012 
PDF, Mobi Page 29
Point 2 of the enumerated list of problems with overengineering (top of page)

This section of the text offers an example of code that is supposed to suffer the problem of being too generic. The example, however, contradicts its own claims, so maybe a better example could be found.

The contradiction is this. First, the example claims that the code in question """treats all input the same?it?s all just bytes. Sometimes this code processes text, and sometimes it processes pictures, but all it knows is that it?s getting bytes."""

Later, the example claims that the code rejects a bad picture: """When the user passes in a bad picture, the error she gets is, ?You passed in bad bytes.? It should have said, ?You passed in a bad picture,? but your code is so generic that it can?t tell the user that."""

Here's the contradiction. How could code that treats all inputs as "just bytes" know that it was given a picture, let alone discern a bad picture from a good picture?

 tmoertel  Nov 03, 2012 
Printed Page 69
9th paragraph (bullet point 5)

There is an unmatched closing double-quote after the word "resource". It is assumed that the word "resource" (alone) is what is intended to be quoted.

 Trevor Cordes  Aug 28, 2012 
81
First paragraph

In "About the Author" section, the correct link is http://www.fedorafaq.org (instead of .com).

Side note: The page number I provided (81) may be wrong as I didn't find a way to display the page number in safari book online viewer. I've tried to infer it from the total page number advertised in the book summary: 82. A desirable feature in my.safaribooksonline.com could be to display the page number. It could HELP people a lot ;-) .

 yves baumes  Nov 29, 2012