| 释义 |
vennersBNC¹⁷³⁹⁹⁵⁺²
基本例句
n.文纳姓氏
Bill Venners: That extra flexibility of composition over inheritance is what I've observed, and it's something I've always had difficulty explaining.
我所发现对象组合所能带来的而继承所不能做到的额外灵活性，而这点也是我一直难于解释的。 yeeyan
Bill Venners: Is the value of patterns, then, that in the real world when I feel a particular kind of pain I'll be able to reach for a known solution?
在现实世界中，当我感受到一种特别的麻烦时，我将能找到一种未知的解决方式。那么这就是模式的价值吗？ yeeyan
Bill Venners: That's funny, because my second question was that I have observed that often people feel the design with the most patterns is the best.
那太有意思了，因为我的第二个问题就是我已经观察到人们经常觉得在设计中用的模式越多就越好。 yeeyan
Bill Venners: What pain?
什么痛苦？ yeeyan
Bill Venners: When do you stop writing tests?
什么时候停止编写测试？ yeeyan
Bill Venners: What explicitness buys me, then, is that it is easier to understand the code.
比尔：明确性真的能让我们更容易理解代码。 yeeyan
Bill Venners: But if it is a100- person team, that means people will be partitioned into groups.
Bill Venners:但这如果是个100人的团队，这就意味着人员将被分配到不同团队中。 yeeyan
Bill Venners: Do you think that quick payback would result if a body of code has absolutely no tests?
比尔：假如一段代码根本没有测试，那么追加测试的成本还能很快收回么？ yeeyan
Bill Venners: So if I write code that talks to the interface of a non- published class, that's a way I am writing to the implementation, and it may break.
那么，当我对一个未发布类的接口进行编程时，我就是在对实现编程咯，而且这个接口随时可能可能失效咯。 yeeyan
Bill Venners: So you invest the time writing tests that you expect to reap back by not fixing bugs.
比尔：也就是说，你花时间在写测试上，然后期待因为不用修漏洞而补回所花的时间。 yeeyan
Bill Venners: What you've described reminds me a bit of brainstorming. You gather some people together to flesh out something you can't clearly see.
比尔：你的描述使我想起了一个小型头脑风暴。聚集了一些人，他们把本不清晰的图景描述出来。 yeeyan
Bill Venners: How do you tell?
比尔：如何区分？ yeeyan
Bill Venners: How does refactoring change the role of upfront design?
比尔：重构如何改变了预先设计的地位？ yeeyan
Bill Venners: How would they categorize a page as wiki maintenance?
比尔：他们怎么把一个页面分类为“维基维护”？ yeeyan
Bill Venners: How does the reader get the big picture of what's all there in a wiki?
比尔：在维基中，读者怎么样获得有关一切的总体轮廓？ yeeyan
Bill Venners: How's that?
那是怎么一回事? yeeyan
Bill Venners: I suppose searching is one way I could begin exploring a new wiki.
比尔：假设搜索是我开始探索新维基的一种方式。 yeeyan
Bill Venners: In your book, Refactoring you say, “The code says everything once and only once, which is the essence of good design.”
比尔：你在《重构》一书中提到：“代码应该实现任何逻辑一次且仅一次，这是良好设计的要素”。 yeeyan
Bill Venners: It sounds like you kind of have to get to know a wiki site.
比尔：听起来你需要去了解一个维基站点。 yeeyan
Bill Venners: So the problem wasn't that these guys had interfaces to their subsystems, the problem was the interfaces were published.
比尔：所以问题不在于团队成员定义了各自的子系统的接口，而在于他们把这些接口看成是发布的接口。 yeeyan
Bill Venners: That was actually my next question: is performance part of the contract?
这恰恰是我预备的下一个问题：契约在操作性能方面如何表述？ www.zszhushuai.blog.ccidnet.com
Bill Venners: Why does it get lost in discussion groups?
比尔：为什么它们在讨论组都会丢失？ yeeyan
Bill Venners: You eventually have to decide on an interface if you are going to publish it.
比尔：如果你要想发布一个接口的话，那么最终还是要把它定下来。 yeeyan |