一位同事从未听说过这个词，我也无法给出一个确切的定义。对我来说，这一直是一个“我看到什么就知道什么”的例子。
附带问题，这个词是谁发明的?
当前回答
重复的代码只会增加不必要的输入层来完成工作。
这些是必要的吗?
在大多数情况下，这些都是结构和装饰性的标记。它提供了代码、函数和语言的一致性。
因此，对于开发人员来说，它有点多余，因为我们已经见过它很多次了，但它确实向非开发人员和编译器传达了一些实际意义。
其他回答
重复的代码只会增加不必要的输入层来完成工作。
这些是必要的吗?
在大多数情况下，这些都是结构和装饰性的标记。它提供了代码、函数和语言的一致性。
因此，对于开发人员来说，它有点多余，因为我们已经见过它很多次了，但它确实向非开发人员和编译器传达了一些实际意义。
样板文件是优秀程序员所避免的:重复。
In practical terms, boilerplate code is the stuff you cut-n-paste all over the place. Often it'll be things like a module header, plus some standard/required declarations (every module must declare a logger, every module must declare variables for its name and revision, etc.) On my current project, we're writing message handlers and they all have the same structure (read a message, validate it, process it) and to eliminate dependencies among the handlers we didn't want to have them all inherit from a base class, so we came up with a boilerplate skeleton. It declared all the routine variables, the standard methods, exception handling framework — all a developer had to do was add the code specific to the message being handled. It would have been quick & easy to use, but then we found out we were getting our message definitions in a spreadsheet (which used a boilerplate format), so we wound up just writing a code generator to emit 90% of the code (including the unit tests).
Joshua Bloch有一个关于API设计的演讲，涵盖了糟糕的API如何使样板代码成为必要。(参考样板文件的第46分钟，今天听这个)
样板代码是指可以反复使用的一段代码。另一方面，任何人都可以说它是一段可重用的代码。
这个词实际上来自钢铁行业。
对于一点历史，根据维基百科:
在19世纪90年代，样板版实际上是铸造或冲压成金属，准备印刷，并分发给美国各地的报纸。直到20世纪50年代，成千上万的报纸从美国最大的供应商西部报业联盟那里收到并使用了这种样板文件。有些公司还以样板文件的形式发布新闻稿，这样它们就必须按书面形式打印出来。
根据维基百科:
In object-oriented programs, classes are often provided with methods for getting and setting instance variables. The definitions of these methods can frequently be regarded as boilerplate. Although the code will vary from one class to another, it is sufficiently stereotypical in structure that it would be better generated automatically than written by hand. For example, in the following Java class representing a pet, almost all the code is boilerplate except for the declarations of Pet, name and owner: public class Pet { private PetName name; private Person owner; public Pet(PetName name, Person owner) { this.name = name; this.owner = owner; } public PetName getName() { return name; } public void setName(PetName name) { this.name = name; } public Person getOwner() { return owner; } public void setOwner(Person owner) { this.owner = owner; } }
