Errata

Misspelled name:

Kufler -> Kuefler

"Google's collective experiences" should be "Google's collective experience"

See “The Boy Scout Rule” and Kevin Henney, 97 Things Every Programmer Should Know (Boston: O’Reilly, 2010).

Kevin -> Kevlin

Note from the Author or Editor:
Footnote 9 in Chapter 3 ("Knowledge Sharing") should be attributed to "Kevlin Henney", not "Kevin Henney".

What does it cost to "not" take action?

Drop the quotations from "not".

missing the word "by":
> This leads directly to nonjokes as illustrated **by** this "Compiling" comic

It says "Chesterson's fence" instead of "Chesterton's fence" - just a typo where an s should be a t.

Note from the Author or Editor:
Confirmed - should change "Chesterson's" to "Chesterton's"

"Such failures are often intentional" should be "Such failures are often unintentional"

"what it does it take to scale yourself into a really good leader?"
should be
"what does it take to scale yourself into a really good leader?"

Note from the Author or Editor:
Confirmed.
Change "what it does it take" to "what does it take".

"Most of these tasks are things that are fairly easy for you do."
should be
"Most of these tasks are things that are fairly easy for you to do."

Note from the Author or Editor:
Confirmed.
"Most of these tasks are things that are fairly easy for you do."
should be
"Most of these tasks are things that are fairly easy for you to do."

"A signal is how you might know that you’ve achieved the end result."
In the other 2 bullet points "goal" and "metric" are in bold, but "signal" here is not in bold.

Note from the Author or Editor:
"signal" in the 2nd bullet should be italicized, to match "goal" and "metric" in the other bullets.

It only shows "Intellectual" but it should be "Intellectual complexity" that appears on the page 131.

Note from the Author or Editor:
"Intellectual" in the first column should be expanded to "Intellectual Complexity".

“Convergent software peer review practices.”
should be
"Convergent contemporary software peer review practices."
for the title of this article.
https://dl.acm.org/doi/10.1145/2491411.2491444

Note from the Author or Editor:
Update the text of footnote #6:
“Convergent software peer review practices.”
should be
"Convergent contemporary software peer review practices."

“Hello World” has established itself is one of the best ways to ensure that all team members start off on the right foot.

It should’ve been:

“Hello World” has established itself as one of the best ways to ensure that all team members start off on the right foot.

“as” instead of “is”

Note from the Author or Editor:
Change "has established itself is one" to "has established itself as one"

"Functional tests", "system tests" are italicized, but for "end-to-end tests" only "end-to-end" is italicized, so the whole "end-to-end tests" should be italicized as well.

Likewise, “unit tests” is in double-quoted but instead it should be italicized as well to match with other test types in this paragraph such as "integration tests."

Misspelled name:

Kueffler -> Kuefler

multiply_postiveAndNegative_returnsNegative
should be:
multiply_positiveAndNegative_returnsNegative
(it says "postive" instead of "positive", it's missing the 'i')

AssertionError: <[red, green, blue]> should have contained <orange>.”
should be
“AssertionError: <[red, green, blue]> should have contained <orange>.”
(The opening double quote is missing)

"A related way that tests shared code is via setup/initialization logic."
This sounds like some shared code is tested, but the section talks about how to share code between tests. So "A related way that tests share code is via setup/initialization logic." would make more sense.

Note from the Author or Editor:
Change "shared code" to "share code"

Overriding values in setup mMethods -> Overriding values in setup methods (It has an extra 'M').

"combinatorically" should be "combinatorially"

Tests of these type... -> Tests of this type...

This is repeated at the beginning of "Performance, Load, and Stress testing" (page 297), "Deployment Configuration Testing" (298), "Exploratory Testing" (298), "A/B Diff Regression Testing" (299), "UAT" (301) and "Prober and Canary Analysis" (301), "Disaster Recovery and chaos Engineering" (302) and "User Evaluation" (303)

The follow paragraph is duplicated twice. The first time it appears on the page 302 in the Limitations section(as the second paragraph). The second time it appears on the page 303 in the Limitations section as the third paragraph:

"If a prober performs a mutable(write) action, it will modify the state of production..."

Note from the Author or Editor:
This is intentional but could still be clarified (to make it clear that it is intentional, rather than just a copy/paste issue).

The second instance (on page 303) should be clarified:
"If a prober performs a mutable (write) action"
should become:
"As with a prober, if a DiRT test performs a mutable (write) action"

"in front of running both these tests and running TAP tests"
should be
"in front of both running these tests and running TAP tests"

"With Google, we occasionally" should be "Within Google, we occasionally"

RedHat should be Red Hat.

“every developer has their own IDE on their own workspace do the indexing
calculation”
should be
“every developer who has their own IDE on their own workspace should do the indexing calculation”

Misspelled Name:

Kueffler -> Kuefler

The diagram has a box for "Clear" that should say "Clean"

Note from the Author or Editor:
The diagram has a box for "Clear" that should say "Clean"

"base a build system around the tenants of functional programming" - "tenants" should be "tenets".

"(which defines how it is referenced on the command line and by other
targets" doesn't have a closing parenthesis.

“However, having a well-defined code review process in only part of the code review story”. in -> is

"Request view" should be "Request review" per the second bullet point below.

Note from the Author or Editor:
Confirmed. In Figure 19-1 the "Request view" box should be "Request review".

wrong spelling

Change publish year from 2004 to 1999.

This is in accordance with the publisher’s webpage: link.springer.com/book/10.1007/978-3-662-03811-6

Note from the Author or Editor:
Agreed.

Update citation in the footnote to end with
"(Germany: Springer, 1999)"

(Also note the typo in "Germany" vs. "Gernamy")

"Dependendencies" should be "Dependencies"

RedHat should be Red Hat.

"nothing that anyone relies upon is change in a breaking fashion."
should be
"nothing that anyone relies upon is changed in a breaking fashion."

"with a given set of infrastructures" => "with a given infrastructure"

"make the most use of Google's" would read more normally as "make the best use of Google's"

"Chapters 20 and 19" should be "Chapters 19 and 20"

"serve the same overall purpose in the developer workflow identify" => "serve the same overall purpose in the developer workflow - to identify"

"An hour ago users, started experiencing more failed requests. Around the same, time the number of retries"
should be
"An hour ago users started experiencing more failed requests. Around the same time the number of retries"

Note from the Author or Editor:
Drop the stray comma in "An hour ago users, started"

"informationL:" => "information:"

"with links to logs, directly to the error message." => "with links to logs, directly in the error message."

"for having a separate serverless stack for a part of a part of the workloads"
Is this "a part of a part of" intentional? If so what does each 'part' mean, or does it just imply it is a very small part of the workloads?

Note from the Author or Editor:
This doesn't seem intentional. Change "for a part of a part of the workloads" to "for a small fraction of the overall workload."