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

3 citations across 3 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.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

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