Software Engineering at Google¶
Winters, T., Manshreck, T., & Wright, H. (2020). Software Engineering at Google: Lessons Learned from Programming Over Time. O'Reilly.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Observable Surface Becomes Contract
- In software and API design, Hyrum's law names it explicitly: with sufficient users, every observable behaviour of an API becomes part of its effective contract.
This sourceStates Hyrum's Law: with a sufficient number of users of an API, it does not matter what you promise in the contract — all observable behaviors of your system will be depended on by somebody.
- In software and API design, Hyrum's law names it explicitly: with sufficient users, every observable behaviour of an API becomes part of its effective contract.
- Rhetorical Velocity
- The recomposition-meaning invariant bites hard in software — the effective meaning of an API is whatever callers actually rely on, not what the author intended, which is why "Hyrum's Law" (every observable behavior of an interface will eventually be depended upon by someone) is the engineering folk-statement of the prime's claim that recomposition, not authorial intent, arbiters meaning.
This sourceStates Hyrum's Law: 'With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody' — the engineering form of the recomposition-meaning invariant.
- The recomposition-meaning invariant bites hard in software — the effective meaning of an API is whatever callers actually rely on, not what the author intended, which is why "Hyrum's Law" (every observable behavior of an interface will eventually be depended upon by someone) is the engineering folk-statement of the prime's claim that recomposition, not authorial intent, arbiters meaning.
Mechanisms¶
- Platform Semantic Versioning and Release Train
- And even a scrupulous, spec-correct change can break someone, because builders inevitably come to depend on observed behavior beyond the documented contract — Hyrum's Law.
This sourceStates Hyrum's Law: with enough users, observable behavior beyond the documented contract will acquire dependents, so even spec-correct changes can break users.
- And even a scrupulous, spec-correct change can break someone, because builders inevitably come to depend on observed behavior beyond the documented contract — Hyrum's Law.
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.
Links previously used in the corpus¶
Before the registry existed this work was also linked 2 other ways.
- https://abseil.io/resources/swe-book ×1
- https://www.oreilly.com/library/view/software-engineering-at/9781492082781/ ×1
Registry ID ref:edd7228a782e · see in the full table