They write documentation because it's important.
他们写文档，因为这很重要。
Ambler: Yes, so we do write documentation, but we treat it like a requirement.
Ambler：是的，我们确实编写文档资料，但是我们将其视为一种必要条件。
We need a little longer to finalize the capabilities, fix bugs, receive feedback, write documentation, release 1.0.0.ga etc.
我们需要更长的时间来确定功能、修改bug、接收反馈、编写文档、发布1.0.0 . GA等等。
A good time to write documentation is when someone in the department gives two-weeks notice: use that time to make sure the departing team member documents all of their code.
部门中的某人还有两周就要闪人的时候是写文档的好时机，这段时间里应该确保将要离开的小组成员为其全部代码写好了文档。
Actually exposing these as configuration fields, however, is not always completely trivial: the developers must choose property names, write documentation, handle types, and choose default values.
然而，将这些公开为配置字段并非都很简单：开发人员必须选择属性名称，编写文档，处理类型，以及选择默认值。
Write the code and documentation.
编写代码和文档。
If you write real documentation, write tests that verify every statement you make in it.
如果你写了实际的文档，写写测试来验证一下其中的陈述。
You can use the LSL documentation to write scripts for objects, and just build objects in the simulator using the standard client.
您可以使用LSL文档为对象编写一些脚本，并在使用标准客户机的模拟器中编译这些对象。
If you are creating a mutable class m, you should be prepared to write a lot more documentation about the treatment of references to m than if m were immutable.
如果您要创建一个可变类m，那么您应该准备编写比m是不可变的情况下多得多的文档说明，以说明怎样处理m的引用。
Fresh out of college, I didn't have enough experience to develop the code, test the code, write the documentation, market the product, or do the usability tests.
我刚刚从学校毕业出来，没有足够的经验去开发代码、测试代码、撰写文档、推销产品、或者做可用性测试。
So we don't write as much documentation up front because that information is going to change.
所以，我们并不事先编写大量的文档，这是由于这些信息是会发生变化的。
Of course, the next thing to do after codifying the program's configuration is to write the documentation — yes, that's right, even before starting on the code.
当然，紧接着系统化程序配置的下一个任务就是编写文档——是的，完全正确，就是在开始编码之前。
Because all of my content is defined in text-based XML, I can easily write scripts that make wide-sweeping changes to the documentation.
由于我的全部内容都是用基于文本的xml定义的，所以我可以轻松地写出令文档发生显著变化的脚本。
If the documentation doesn't cover every API, you are forced to write characterization tests.
如果文档不能覆盖所有API，你将不得不编写特性化的测试。
If you have taken the time to write proper POD documentation in your binaries and modules, you will gain the benefit of automatic documentation generation.
如果已经花时间在二进制文件和模块中编写正确的POD文档，则将获得自动文档生成的好处。
Given protocol documentation and a whole lot of free time, you could in theory write an entirely new implementation that would communicate with the server.
有了协议文档和大量空闲时间，您可以从理论上编写一个与服务器通信的全新实现。
It really motivates you to write very tight and concise documentation.
它促使您编写更加严密和简练的文档资料。
Switching from a manual writing task to an automated process for generating technical documentation requires the administrators to write programs and scripts for automating these processes.
从手工编写文档转换到自动生成技术文档要求系统管理员编写自动执行这些过程的程序和脚本。
I met with the documentation team, making sure they understood how to write a good tutorial and reference for Excel Basic.
我需要同文档团队合作保证他们明白如何编写高质量的教程和参考手册。
You write whatever documentation you need for other people to (re) use your products and services.
你记录他人重用你的产品和服务时必需的任何文档。
Good documentation is hard to write.
要想写好文档很难。
While documentation was certainly provided, the general populace never got the in-depth to really explore the nooks and crannies of the language, let alone write their own compiler.
虽然微软提供了文档，但一般的开发人员不可能真正深入到语言的底层，更不用说编写自己的编译器了。
In addition to basic documentation, you'll probably write types that are specific to a certain member type, or perhaps a certain set of member types.
除了基本的文档外，可能还要针对某个特定的成员类型或者一组成员类型编写类型。
Take some time to peruse this documentation, because you will eventually need to write AST code for some of your more advanced rules.
请花一些时间研读这一文档，因为您最终将会为您的高级规则编写AST代码。
To learn how to write Products, you're going to have to read much more documentation (most of it still in progress) and, frankly, study existing Products to see how they're done.
要学会怎么写Product，您还得阅读更多文档（其中有很多仍在完善之中），坦率地说，还要研究已有的 Product，看看它们是怎么做的。
You could, for example, write a doclet that produces PDF documentation instead of the standard HTML output.
例如，您可以编写一个doclet来生成pd f文档，而不产生标准HTML输出。
One of the benefits of the broader adoption of Eclipse is that more documentation is available, making it easier to write plug-ins.
更多采用Eclipse的好处之一是，能够使现有的更多文档可用，使编写插件更容易。
Wikis are highly convenient for the particular task of writing documentation, and you would be hard-pressed to write as efficiently in raw XML.
Wikis对于特定的文档编制任务非常方便，您将会顽固地坚持用原始的 XML有效地编写代码。
Besides, who wants to write a documentation tool when one already exists and works fine for the most part?
另外，当已经存在文档编制工具，并且在大多数时候都工作得很好时，谁还要编写文档编制工具？
Besides, who wants to write a documentation tool when one already exists and works fine for the most part?
另外，当已经存在文档编制工具，并且在大多数时候都工作得很好时，谁还要编写文档编制工具？
应用推荐