因此我们真的不知道我们所创建的可重用组件是否是一件很好的事情，直到有人使用我们的组件，然后又有人重用。
So until someone USES our component, and then someone reuses it, we really don't know if we've done a good job of creating something reusable.
是否每个人都认同可重用资产的单一行为集，或者每个人都采用自己的自定义版本，实际上完全不能进行重用？
Can everyone really agree on a single set of behavior for a reusable asset, or will everyone have their own customized version which isn't really being reused after all?
它也可以用于项目名之后，是否使用取决于您对可重用性的计划(见“根据可重用性命名”)。
It may or may not be used in addition to the project name, depending on your plans for reusability (see "Naming for reusability").
是否有团体在考虑跨功能应用程序的可重用性？
Is there a body that looks at cross-functional application reusability?
将某些内容变为可重用的，是否会给现有的设计带来重大变化？
Will making something reusable add significant change to the existing design?
将某些内容变为可重用的，是否会给现有的设计带来重大变化？
Will making something reusable add significant change to the existing design?
应用推荐