样板文件是一种写作单元，可以不作任何更改地反复使用。通过扩展，这种思想有时应用于可重用编程，如“样板代码”

“样板代码”是任何看似重复的代码，它们一次又一次地出现，以获得一些看起来应该简单得多的结果。

这是一个主观的定义。

这个术语来源于报纸行业的“标准版”:wiki

软件开发中的样板对不同的人有不同的含义，但通常是指反复使用的代码块。

在MEAN栈开发中，这个术语指的是通过使用模板来生成代码。它比从头开始手动编码整个应用程序更容易，它提供了代码块的一致性和更少的错误，因为它是干净的，经过测试和验证的代码，而且它是开源的，所以它不断更新或修复，因此它在使用框架或代码生成器时节省了大量时间。有关MEAN stack的更多信息，请点击这里。

在词源上，术语boilerplate: from http://www.takeourword.com/Issue009.html…

Interestingly, the term arose from the newspaper business. Columns and other pieces that were syndicated were sent out to subscribing newspapers in the form of a mat (i.e. a matrix). Once received, boiling lead was poured into this mat to create the plate used to print the piece, hence the name boilerplate. As the article printed on a boilerplate could not be altered, the term came to be used by attorneys to refer to the portions of a contract which did not change through repeated uses in different applications, and finally to language in general which did not change in any document that was used repeatedly for different occasions.

编程中的样板文件由什么组成?正如其他人可能已经指出的那样，它 只是一大块代码，一遍又一遍地复制，很少或 在这个过程中没有对它做任何改变。

从维基百科:

在计算机编程中，样板文件是用来描述必须包含在许多地方且很少或没有更改的代码段的术语。它更常用于被认为是冗长的语言，即程序员必须编写大量代码来完成最少的工作。

所以基本上，你可以把样板代码看作是一种编程语言所需要的文本，在你用这种语言编写的程序中经常用到。

现代语言正在尝试减少它，但旧的语言也有特定的类型检查器(例如OCaml有一个类型推断器，它允许您避免在像Java这样更冗长的语言中作为样板代码的太多声明)

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).