Patterns for managing source code branches¶
M., F. (2020). Patterns for managing source code branches. martinfowler.com.
Cited by¶
1 citation across 1 artifact.
Primes¶
- Branching and Merging
- Naming the full cycle reframes the branch as a debt deliberately incurred against a future reconciliation, and the merge as the moment that debt comes due.
Supported in partVerified against the work's full text
Fowler says branching buys isolation whose price comes due at integration, and that merging gets harder as branches diverge; he never uses the word debt.
“And so we give individuals the illusion of frozen time, that they are the only ones changing the system and those changes can wait until they are fully baked before risking the system. But this is an illusion and eventually the price for it comes due.”
- Naming the full cycle reframes the branch as a debt deliberately incurred against a future reconciliation, and the merge as the moment that debt comes due.
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? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
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:6e9f197d106a · see in the full table