Some commentators have said that contracts are like computer software . One way in which the analogy is accurate is that contract forms represent the “codified experience”  of others. And like any experience, some of the lessons learned are likely to be more valuable than others — with some lessons not being applicable and possibly even being counterproductive. Which of course is just another way of reiterating that drafters shouldn’t blindly reuse contract forms.
 See, e.g., Steve Smith, 9 Ways Contract Lawyers are Like Software Developers (2010). The analogy goes only so far: unlike the people who must carry out the instructions in a contract, people, computers don’t get buyer’s remorse or otherwise have to be persuaded to carry out their instructions.
 See, e.g., Peter Eeles & Peter Cripps, The Process of Software Architecting ch. 2 (Addison-Wesley Professional 1st ed. 2009), excerpt at Google Books,