It's extremely difficult to change this type of poor agility in an organization, so protect yourself and keep written documentation of where your time is being spent.
要改变组织中的此类糟糕的敏捷性是极其困难的，因此要保护您自己，并保留有关您的时间都花在何处的书面文档。
It suffers from a lack of documentation, so learning took more time than I would have liked.
由于它目前缺少文档，所以学习它花的时间比我期望的要多。
Writing documentation takes time and most administrators do not have the time to document fully changes to every system on an immediate basis.
编写文档要花费时间，而大多数管理员没时间及时地在文档中完整地记录对每个系统的更改。
When I manage software development projects, much of my time is spent on "content wrangling" that organizes and prepares documentation such as use cases.
我管理软件开发项目时，大部分时间花在“内容争论”上，即组织和准备诸如用例之类的文档。
On the other hand, if the time is for documentation purposes, then you may not need to convert the time to other local interpretations.
另一方面，如果时间是以文档记录为目的的，那么可能不需要把时间转换成其他的当地时间。
By creating many of their artifacts according to this principle, they avoided squandering time and attention on documentation that wasn't necessary for delivering a stable, well-tested product.
通过根据这个原则建立许多工件，他们避免了为交付一个稳定、测试良好的产品而在不必要的文档上浪费很多时间和精力的情况。
They must plan sufficient time for transition to production, various levels of testing, documentation, and so on, as shown in Figure 1.
他们必须设计过渡到产品的具体时间，测试的各种水平，以及文件等等，如图1所示。
If there is not enough time for testing, the first thing to do is reallocate the effort used in requirements documentation to writing customer tests.
如果没有足够的时间来进行测试，则首先要重新分配在需求文档中编写客户测试所投入的精力。
System administrators should spend their time writing automation processes for generating documentation, not writing documentation.
系统管理员应该花时间编写生成文档的自动化过程，而不是编写文档。
The XSL transforms provided with this article (see Download) are an extension of an open source project I developed five years ago as an attempt to shorten both documentation and QA time.
本文附带提供的XSL转换(参见下载)是我五年前开发的一个开源项目的扩展，那时我旨在缩短文档化和QA时间。
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.
有了协议文档和大量空闲时间，您可以从理论上编写一个与服务器通信的全新实现。
Documentation takes time and requires communication, potentially reducing efficiency.
编制文档占用时间，并需要交流，可能降低效率。
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文档，则将获得自动文档生成的好处。
However, for most documentation groups, what you save in time and accuracy and gain in consistency can provide huge benefits, especially if you manage larger documentation sets.
不过，对大多数文档组而言，一致性能够节省时间和保持准确，尤其是管理大型文档集时，其益处是非常明显的。
In addition, increases in system complexity over time, tight development schedules that force poor design decisions, and lack of system documentation can compound the problem.
另外，随时间而增长的系统复杂性、紧张的开发进度、不好的设计决策、短缺的系统文档，这些都使问题显得更加突出。
Any time spent by a system administrator writing documentation is wasted effort, because the moment the documentation is complete, it is obsolete.
系统管理员编写文档花费的时间实际上是浪费了，因为文档完成之后马上就过时了。
Once associated with a program entity, an attribute can be queried at run time and used in any number of ways (for example, help documentation).
属性一旦与程序实体关联，就可以在运行时查询它，并且可以以各种方式使用(例如，帮助文档)。
When you've completed all the research and documentation for your organization's processes and incorporated that information into your design, it's time to make your recommendations.
当您完成组织流程的所有研究和文档并将该信息整合进设计中时，就到了提出建议的时候了。
The communication part of the architecture documentation includes communicating to management, developers and communicating across time (project life cycle).
架构文档的交流部分包括与管理层，开发者们沟通和在软件生命周期中的交流。
In writing my own user documentation, I found I was spending quite a bit of time simply copying and pasting text throughout the document.
在编写自己的用户文档时，我发现大量的时间都浪费在文档内部的复制、粘贴上。
If you haven't begun creating documentation prior to starting this step, it's time to start.
如果在开始本步骤之前还没有开始创建文档，现在应该开始了。
Manually written technical documentation is usually a tedious, boring, and time consuming task.
手工编写技术文档通常很乏味、无聊而且很耗时间。
The club this afternoon received notification from the Football Association of their decision to charge Luis Suárez and will take time to review properly the documentation which has been sent to us.
俱乐部今天下午已经收到英足总的决定起诉苏亚雷斯的通知书，我们将妥善处理英足总发给我们的文件。
Take some time to peruse this documentation, because you will eventually need to write AST code for some of your more advanced rules.
请花一些时间研读这一文档，因为您最终将会为您的高级规则编写AST代码。
Maintain documentation: If you haven't begun creating documentation prior to starting this step, it's time to start.
维护文档：如果在开始本步骤之前还没有开始创建文档，现在应该开始了。
If you've ever tried to put some HTML or XML into an XML document, maybe as documentation, you've run into this problem as soon as it comes time to include an example.
如果您曾经尝试过将一些HTML或XML放到一个XML文档(也许作为文档资料)中，那么只要您试图包含一个示例，就会遇到这个问题。
Simplicity saves documentation, training, and support time.
“简单”节约了书写文档、培训和提供支持的时间。
And, as with most Domino applications, better documentation would help save a lot of time and effort getting started.
另外，正如大部分Domino应用程序一样，更好的文档可以在您入手时帮助您节省大量的时间和努力。
The Python documentation is in tutorial form, which I don't particularly like, but if take time to read it, you'll find the answers to a lot of your Python questions.
Python文档是教程格式的，我不是特别喜欢这种格式，但如果花点时间去读，您将可以从中找到很多Python问题的答案。
The Python documentation is in tutorial form, which I don't particularly like, but if take time to read it, you'll find the answers to a lot of your Python questions.
Python文档是教程格式的，我不是特别喜欢这种格式，但如果花点时间去读，您将可以从中找到很多Python问题的答案。
应用推荐