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 strong code ownership, there's my code and your code. I can't change your code.
在强代码所有权中,严格区分我的代码和你的代码,我不能改动你的代码。
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.
在这个例子中,缓冲区的所有权已经被有效地转移,因而进行调用的代码必须假设在被调用方法返回时缓冲区已经被删除。
Developers new to collective code ownership often are overwhelmed by the amount of code that they have to learn.
刚接触集体代码所有制的开发者很容易被他们不得不掌握的代码的数量吓倒。
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.
在本文中,我们会集中讨论五个主要问题,即:特性团队、团队自主管理、业务价值、代码所有权以及稳定性。
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!
现在回想起来,集体性的代码所有权非常有用。
That's why strong code ownership doesn't go well with refactoring, but weak code ownership works fine with refactoring.
这就是强代码所有权下不适合做重构而弱代码所有权下可以做重构的原因。
With weak code ownership, there's my code and your code, but it is accepted that I could go in and change your code.
弱代码所有权中,还是会区分代码的所有者,不同的是它允许开发者改动其他人的代码。
Typically code ownership will be partitioned among the developers.
一般的代码所有权会在开发员之间进行分配。
What does code ownership mean, and what is bad about having a strong sense of it?
代码所有权是什么意思,强代码所有权有什么缺点?
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对此调整。
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.
明确回答这个问题是困难的,因为这与团队的组织方式、如何处理代码所有权问题等有很大关系。
Jeff DE Luca also takes a strong stand against collective code ownership.
JeffDeLuca也不完全赞同集体代码所有权。
Collective ownership (Maps to collective code ownership).
集体所有权(映射到集体代码所有权(collective code ownership))。
Collective Code Ownership (doubtful).
集体代码拥有权(值得怀疑)。
Rugged code is a way of breaking through and instilling a mindset that secure code should be a pride-of-ownership issue just as much as elegant, high performing, and high quality code is.
坚固的代码是一种突破,并注入这样一种心态:安全的代码同样应该成为引以为傲的源泉,就像优雅的、表现出色的高质量代码一样。
Keats says being able to see the software's source code, or computer language code, and being able to rewrite or make changes gives users a sense of ownership.
济慈说软件源代码或电脑机器码可见性,以及软件可以任意重编或修改,这些都能使用户产生自主感。
Even if Skype's founders had won their legal IP claims — they eventually settled, in exchange for an ownership piece — the buyers likely believed they could rewrite the necessary code.
即便Skype创始人真的赢了知识产权诉讼案——他们最终达成了和解,换取部分股权——这些投资人可能也相信他们能重写所需的代码。
As you can see, the SwingBuilder's judicious use of closures allows you to see the chain of ownership clearly and declaratively in code.
可以看到SwingBuilder使用了闭包,这让我们可以清晰地看出拥有关系链。
Collective ownership encourages the entire team to work more closely together: each individual and each pair strives a little harder to produce high-quality designs, code, and test cases.
共同所有鼓励整个团队更加紧密协作:每个个人和每个双人更努力生产高质量设计、代码和测试集。
But strong code ownership and refactoring are a right pain in the butt, because a lot of the refactorings you want to make you can't make.
但是采用强代码所有权进行代码的重构是个不折不扣的笑柄,原因就是重构中不能随便改动不属于自己的代码。
But strong code ownership and refactoring are a right pain in the butt, because a lot of the refactorings you want to make you can't make.
但是采用强代码所有权进行代码的重构是个不折不扣的笑柄,原因就是重构中不能随便改动不属于自己的代码。
应用推荐