在这个例子中，缓冲区的所有权已经被有效地转移，因而进行调用的代码必须假设在被调用方法返回时缓冲区已经被删除。
In this case, the ownership of the buffer has been effectively transferred, and the calling code must assume the buffer to have been deleted when the transferee method returns.
直到用户交互或代码明确地设置了焦点所有权为特殊的组件，才丢弃所有的键事件。
All key events are discarded until user interaction or code explicitly sets focus ownership to a particular component.
在本文中，我们会集中讨论五个主要问题，即：特性团队、团队自主管理、业务价值、代码所有权以及稳定性。
In this article, we focus on five main issues, namely: feature teams, team autonomy, business value, code ownership, and stability.
每个人都负责这一事实消除了无代码所有权所带来的混乱。
The fact that everybody is responsible negates the chaos that ensues from no code ownership.
每个人都负责这一事实消除了无代码所有权所带来的混乱。
The fact that everybody is responsible counteracts the chaos that ensues from no code ownership.
建立您的项目环境来支持集体代码所有权，利用最佳人选完成项目。
And set up your project environment to enable collective code ownership, leveraging the best of all the people on the project.
这幅图描绘了代码基础是如何被分割到模块中用于强壮的架构和所有权的。
This figure illustrates how code bases are separated into modules for strong architecture and ownership.
某些实践例如严格的代码所有权或瀑布过程，可能会与重构背道而驰。
Some practices, like strict code ownership or a waterfall process, can play against refactoring.
现在回想起来，集体性的代码所有权非常有用。
Looking back, it was collective code ownership at its finest!
一般的代码所有权会在开发员之间进行分配。
Typically code ownership will be partitioned among the developers.
而私有代码所有权的益处在于。
对代码和产品所有权意识。
明确回答这个问题是困难的，因为这与团队的组织方式、如何处理代码所有权问题等有很大关系。
It's a difficult question to answer specifically because it has a lot to do with how your team is organized, how you deal with code ownership issues, and so on. However, here are some guidelines.
JeffDeLuca也不完全赞同集体代码所有权。
Jeff DE Luca also takes a strong stand against collective code ownership.
集体所有权(映射到集体代码所有权(collective code ownership))。
假如他们采用弱代码所有权的话，就不会有任何问题。
If they had had weak code ownership, there would have been no problem.
集体代码所有权：没有单独的一个人能“拥有”一个模块，所有开发者都能在任何时候针对代码库的任何部分进行工作。
Collective code Ownership: No single person "owns" a module. Any developer is expect to be able to work on any part of the codebase at any time.
在这种所有权中，团队中任何人都不具有对代码的所有权。
In this style, no code is assigned to any particular person on the team.
在强代码所有权中，严格区分我的代码和你的代码，我不能改动你的代码。
In strong code ownership, there's my code and your code. I can't change your code.
在BSD许可下，该公司可以保持其代码的所有权，所以公司b将无法在其新的电话中使用相同的代码。
Under the BSD license, the company can keep this code proprietary so that company B can't use the same code for their new phone.
弱代码所有权中，还是会区分代码的所有者，不同的是它允许开发者改动其他人的代码。
With weak code ownership, there's my code and your code, but it is accepted that I could go in and change your code.
这就是强代码所有权下不适合做重构而弱代码所有权下可以做重构的原因。
That's why strong code ownership doesn't go well with refactoring, but weak code ownership works fine with refactoring.
代码所有权是什么意思，强代码所有权有什么缺点？
What does code ownership mean, and what is bad about having a strong sense of it?
缺乏代码所有权，缺乏经验以及我们对单元测试的依赖，有时会产生不当的代码，但是随后的项目重审时会用refactoring对此调整。
Lack of code ownership, inexperience, and our (correct) reliance on the unit tests, did sometimes result in inelegant code, but refactoring later in the project cycle rectified this.
缺乏代码所有权，缺乏经验以及我们对单元测试的依赖，有时会产生不当的代码，但是随后的项目重审时会用refactoring对此调整。
Lack of code ownership, inexperience, and our (correct) reliance on the unit tests, did sometimes result in inelegant code, but refactoring later in the project cycle rectified this.
应用推荐