Kirk further mentions an interesting way to do reviews, called the 20% review.
Kirk还提到了一种用来进行复查的有趣方式，名为20%复查。
The teacher will most likely do review in the first 10-15 minutes of the class. This gives you a chance to perfect the previous lesson's material and address any problems.
通常老师在上课前10-15分钟会在班级中进行复习，这是一个很好的机会来完善先前课堂的内容并且发现问题的所在并改正。
Do you need to review some prior materials that provide foundations for the content you are now studying?
你要复习一些以前的材料来为你在学习的新内容牢固基础吗？
I'm supposed to do a literature review for my psychology course, but I'm having a hard time finding articles.
我应该为我的心理学课程做文献回顾，但是很难找到文章。
To do well in your exams this year, turn off the TV, silence your mobile, and review your work regularly.
要想在今年的考试中取得好成绩，关掉电视，把手机调成静音，定期复习功课。
At that point, the New York Review swung into action, and they did what they always do in these circumstances.
对此，《纽约书评》立即采取了行动，做了在这种情况下他们以往经常做的事。
A: Do you have the checklist for feasibility review?
A：你那儿有可行性分析审核的检查清单呢？
By the way, in this review, I looked for what was obvious or easy to do — I am sure that other things are possible beyond what my passing efforts accomplished.
顺便说一句，在本次评论中，我所寻找的是明显的或者容易去做的内容——的确，除了我努力去完成的内容以外，其他的事情也是可能的。
But they do not explain the circumstances under which a user will be outed as having written a particular rating or review.
但是他们没有解释在哪种情况下一个用户因为写了某些特别的评级或评论而会被除名。
You should review the single changes and decide if they do make sense for your system.
您应该检查每一项修改，确定它们对系统是否有意义。
Make it a habit to do weekly or monthly review. Use Numbers to help you track results.
养成每周或每月回顾总结的习惯，用数据来帮助你跟踪结果。
A developer would have to review the migrations to make sure they do what you intended, and deploy them, but writing migrations from hand is probably not something that you'd have to do anymore.
开发者应该检查迁移脚本是否做了你希望做的事情，然后部署即可，但是编写迁移脚本并不是表示你可以做个甩手掌柜，我们必须很清楚有一些额外情况需要处理，例如可能会出现崩溃或者引起歧义的问题。
Do we need to review our projects in Internet Explorer 6? Can we stop supporting IE6?
是否需要在InternetExplorer6中审核我们的项目？我们能否不支持IE6 ？
Before we look at two ways you can do this, let's review how to create a rendering set.
在我们讨论实现这一目标的两种方法之前，先来回顾一下如何创建呈现集？
Let's review how to do this, starting from the plug-in writer's point of view. Just create your plug-in, add com.tools.logging to its dependency list, and create a Log4j configuration file.
现在让我们回顾一下整个过程是如何实现的，我们从插件编辑器的角度入手，创建插件，并将com . tools . logging添加到从属类型列表中，然后创建一个Log4j配置文件。
For physical inputs, make sure everyone knows where to put things that they want you to see and do something about - mail, documents to review, research material, whatever.
在物质投入之前，确定每个人知道往哪里放他们想要让你去看去处理的东西—邮件，文档回顾，研究材料，任何什么。
Generally, you do not need to review them when using the archive to troubleshoot a problem, but they are useful when debugging the automated collector behavior itself.
一般来说，在使用存档解决问题时，您不需要检查它们，但是在调试自动化收集器行为自身时它们是有用的。
Before we discuss the activities associated with the review and refinement of requirements, let's address "why" you need to do this.
在我们讨论与评审和细化需求相关的活动之前，让我们提出一个问题，您“为什么”需要这样做。
Periodically review the dependencies to ensure that your builds do the right amount of work.
应该定期检查任务的从属关系以保证构建工作得到正确执行。
It is a peculiar fact that those who most often express this reluctance do not have the time to measure and objectively review their own time expenditure.
一个很奇怪的事实是，那些经常表示他们这个问题的人却没有时间度量和客观地回顾一下他们自己的时间支出。
Although RUP does a fine job of describing the Development Case and Review Record, it does not fully explain their interrelationship — something I will do in this article.
虽然RUP很好的描述了开发案例和评审记录，但是它没能完全解释它们间的关联关系——这正是本文后面所要讨论的。
Many customers do not have code or architecture review processes.
许多客户没有代码或架构评审过程。
What if a team leader depends on E-mail as the notification that it is time to do a code review?
如果一个团队的领导将电子邮件当作提示参加代码评审会的通知，会怎么样？
Every year we do a review of the top Internet companies, to identify the ones that had the biggest impact.
每年，我们都会重温一下那些顶级的互联网公司，来看看他们中谁才是最具影响力的。
In all of the projects that we looked at in our review, an overarching problem presented itself: it took many lines of code to do simple things.
在我们研究中查看的所有项目，本身都出现一个突出的问题：花费许多行代码行来做简单的事情。
That's certainly effective, but I've found that if teams do a good job using metrics for a continuous review, holding the 20% review for each major system function is sufficient.
它的效果确实不错，不过如果开发团队可以成功地使用度量标准进行持续复查，那么针对每一个主要的系统功能进行20%复查就足够了。
That's certainly effective, but I've found that if teams do a good job using metrics for a continuous review, holding the 20% review for each major system function is sufficient.
它的效果确实不错，不过如果开发团队可以成功地使用度量标准进行持续复查，那么针对每一个主要的系统功能进行20%复查就足够了。
应用推荐