开发人员对这种反馈非常抵触。
补丁开发人员在此期间反应灵敏是至关重要的。
It is vitally important that the patch developer is responsive during this period.
准确来讲是，测试人员和开发人员完全对立来坐。
Literally, the testers and the developers sat on opposite sides on the table.
一般来说，每个软件开发项目都有一组测试人员和一组开发人员。
Generally speaking, every software development project has a group of testers and a group of developers.
更重要的是，它允许程序开发人员在需要时改进账单行为和知识库。
More importantly, it allows the program developers to improve bills behavior and knowledge base when needed.
现在，测试人员和开发人员之间的这种差异可能会导致出现一些摩擦。
Now, this difference between the testers and the developers can lead to an environment where there is a bit of friction.
在分离项目组时，我们会让开发人员和测试人员在一起进行缺陷讨论会议。
During Project Split, we had defect meetings where the developers and the testers met together.
如果您这样做，则应当注册它，以便其他开发人员可以编写组件来与您的组件通信。
If you do so, you should register it so that other developers can write components to communicate with yours.
即使存在限制，一些有创意的开发人员也有可能将立方体卫星技术往有害的方向发展。
Even with constraints, it is possible for some creative developers to take the CubeSat technology in directions that result in harmful outcomes.
许多开发人员使用称为后测试开发（TAD）的各种测试，你首先编写代码，然后编写单元测试。
Many developers use a variant of testing called test-after development (TAD), whereby you write the code and then write the unit tests.
当开发人员审查物件时，他们倾向于抓住任何他们看到的小错误，不管它对迭代的成功有多重要。
When developers review things, they have a tendency to pounce on any little mistake they see regardless of its importance to the success of the iteration.
在早期，我们将应用程序交给顾客之前，我们的开发人员就利用 RAD 进行了最初的单元测试。
Early on, our developers used RAD for the initial unit testing before we turned the application over to the customer.
这家总部位于休斯顿的环境服务公司目前正试图填补1500个职位空缺——从软件开发人员到垃圾车司机。
The Houston-based environmental services company is currently trying to fill 1,500 positions—from software developers to garbage truck drivers.
另一种是找到确保软件开发人员编写的代码中有更少的缺陷的方法，这样黑客就有更少的安全漏洞可以利用。
Another is to find ways to ensure that software developers produce code with fewer flaws in it so that hackers have fewer security holes to exploit.
对于有兴趣将ROO框架作为其软件开发过程中的一部分的Java 开发人员，有哪些推荐的最佳实践？
What are the recommended best practices for Java developers who are interested in using ROO framework as part of their software development process?
我四处走动，与开发人员交谈，有几个人引用了玛丽亚·蒙台梭利的一句名言：“人类才智由双手的使用而发展。”
I walked around and talked with developers, and several quoted a famous saying of Maria Montessori's, "The hands are the instruments of man's intelligence."
我参与了开发人员的会议，其中部分原因是这组特定的父母的对互动媒体很感兴趣，我希望他们可以帮助我解决这个问题。
I had come to the developers' conference partly because I hoped that this particular set of parents, enthusiastic as they were about interactive media, might help me out of this problem.
它们仍然受到资助者、发行供应商和一系列规则的限制——所有这些都约束了CubeSat开发人员所能做和不能做的事情。
They're still constrained by funders, launch providers and a series of regulations-all of which rein in what CubeSat developers can and cannot do.
他们仍然受到来自资助者、发射供应商和一系列法规的限制，所有这些都限制着CubeSat开发人员可以做什么，不能做什么。
They're still constrained by funders, launch providers and a series of regulations—all of which rein in what CubeSat developers can and cannot do.
我称其中一个为“分离项目组”——开发人员组和测试人员组很难共事。
One, which I'll call Project Split—the testing and development teams did not work well together.
那么，企业开发人员应该怎么做呢？
集成开发人员将负责实现这些组件。
The integration developer would be responsible for implementing these components.
开发人员使用软件工具完成工作。
组件模型对开发人员来说是极好的。
组件开发人员和集成开发人员。
开发人员然后将此资产提交到存储库。
作为开发人员，您必须了解这些限制。
UI促使开发人员编写代码。
这对于开发人员非常方便。
开发人员：(后来)“您能帮帮我吗？”
应用推荐