Extreme Programming Explained¶
Beck, K. (2000). Extreme Programming Explained: Embrace Change. Addison-Wesley.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Progressive Refinement from Core Model
- Beck's (2000) Extreme Programming Explained instantiates this clarity discipline in software practice: simple design (start with the simplest baseline that works), refactoring (systematic improvement with automated tests ensuring behavioral invariance), and pair programming (explicit externalization of the choice of baseline and rationale for each refinement).
This sourceFormalization of simple design (minimal baseline) and continuous refactoring (disciplined correction) as core practices.
- Beck's (2000) Extreme Programming Explained instantiates this clarity discipline in software practice: simple design (start with the simplest baseline that works), refactoring (systematic improvement with automated tests ensuring behavioral invariance), and pair programming (explicit externalization of the choice of baseline and rationale for each refinement).
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. The single citation of this work carries no 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.
Registry ID ref:2d8d5986bf80 · see in the full table