|
|
|
|
|
|
by juancb
1467 days ago
|
|
|
If we ignore the value judgement and instead look at maintaining a sufficiently large codebase then, yes. In the below paper an example given is migrating from one API to another. The paper describes a semantically-aware large-scale tool for refactoring a Google sized codebase using map-reduce. Given the externally visible churn in Google products it isn't much of a stretch to imagine they have similar or worse internal churn. In fact I have heard from xooglers that it was common place to internally have competing systems in different states of development and adoption. https://research.google.com/pubs/archive/41342.pdf |
|
|