Editing Code reuse (section)

== Criticism ==
Code reuse results in [[Coupling (computer programming)|dependency]] on the component being reused. [[Rob Pike]] opined that "A little copying is better than a little dependency". When he joined [[Google]], the company was putting heavy emphasis on code reuse. He believes that Google's [[codebase]] still suffers from results of that former policy in terms of compilation speed and maintainability.<ref>{{Citation|last=The Go Programming Language|title=Go Proverbs – Rob Pike – Gopherfest – November 18, 2015|date=2015-12-01|url=https://www.youtube.com/watch?v=PAAkCSZUG1c |archive-url=https://ghostarchive.org/varchive/youtube/20211222/PAAkCSZUG1c |archive-date=2021-12-22 |url-status=live|accessdate=26 February 2016}}{{cbignore}}</ref>

Reusable code requires usually more effort to write and design. [[Fred Brooks]] discusses the significantly higher cost associated with that effort in his essays "The Tar Pit" and "[[No Silver Bullet]]" The fallacy is that effort is often spent without careful understanding of the mechanisms through which that cost will be redeemed. The justification often comes from incorrectly drawing parallels to reusable parts in a physical manufacturing process. Incorrect because writing code is analogous to design of a single product rather than production of multiple units.