The Pragmatic Programmer

Hunt, A., & Thomas, D. (1999). The Pragmatic Programmer: From Journeyman to Master. Addison-Wesley.

Type

Book

Intellectual base

Textbook

Year

1999

Link

https://books.pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/

Cited from

art_aesthetics, organizational_management

Cited by

4 citations across 4 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Broken Windows Theory
  • Software engineering — tolerated bad code, dead comments, ignored warnings, and unmaintained tests lower the perceived cost of adding more bad code, producing codebase decay; zero-warnings policies invert the loop.

    This sourceApplies the broken-windows metaphor to software: tolerated bad code lowers the bar for more, and prompt repair (no 'broken windows' left unfixed) prevents codebase decay; the zero-warnings discipline inverts the loop.

• Minimalism
  • Lean architectures and frameworks: preferring concise code structures that eliminate abstraction overhead and unnecessary complexity (Kernighan & Pike's Practice of Programming; Hunt & Thomas's Pragmatic Programmer

    This sourcePragmatic-engineering tips emphasizing DRY, orthogonality, and minimal-surface design as a discipline of code minimalism.

Domain-specific

• Sequential Coupling
  • If the contract is absent or unenforced, a caller can compile successfully yet encounter an exception, silent no-op, corrupt result, or delayed failure.

Mechanisms

• Product Space Generator Script
  • Making the axis declaration the single source of truth is exactly what stops the drift

    This sourceShows that duplicated representations drift into contradiction when one copy changes and another is overlooked.

Verification

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Not recorded. Neither this nor any other of the 4 citations of this work carries a recorded support check.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Links previously used in the corpus

Before the registry existed this work was also linked 1 other way.

• https://books.google.com/books/about/The_Pragmatic_Programmer.html?id=Z1gCtAEACAAJ ×1

Registry ID ref:4b5417d8d2b8 · see in the full table