Text search: Find fixes within fix Central by entering keywords, error messages, exceptions, and other elements.
文本搜索：通过输入关键字、错误消息、异常和其他元素在FixCentral中查找修复。
If you support only one fix level, it may quite literally be impossible to find fix levels compatible across multiple products.
如果您仅支持一种修复级别，那么很可能无法找到同时兼容于多种产品的修复级别。
There's another way you can find fixes in fix Central, which you might have already discovered: Web links from other IBM support sites that link to fix Central.
还可以通过另一种方法在FixCentral找到修复，您可能已经发现了这个方法：即从其他IBM支持站点链接到Fix Central的Web链接。
As we use them so often, we have more chances to find problems, and furturemore, to fix and improve them.
当我们如此频繁地使用它们时，我们就有更多的机会发现问题，并进一步解决和改进它们。
If an open fire or cooking causes smoke in your home, find a way to fix it.
如果明火或烹饪导致室内产生烟雾，要想办法解决。
For example, one customer routes a task to an administrator to look at fixed-width data feeds when the data fails so that they can find the errant characters and fix or delete them.
例如，一位客户在数据失败时将一个任务路由到管理员，请求管理员检查固定宽度的数据提要，以便找到错误的字符，修复或删除它们。
At this point, you should be able to test that the cloud version of your application works just as well as the production version; fix any problems you find.
此时，您应该能够通过测试确保您的应用程序的云版本与生产版本的效果一样好并修复您发现的任何问题。
If you're going to all of the trouble of reviewing code to find bugs, it certainly makes sense to fix them!
如果您遇到了评审代码以找到缺陷的所有问题，那么修复它们就变得顺理成章了！
So in a matter of minutes, ARE can find and fix (yes, it can correct issues for you!) the authority issue that is causing your application to fail.
在几分钟之内，ARE 就能发现并修复（没错，ARE能够为您修复问题）导致应用程序失败的权限问题。
The performance and problem analysis tools help you find and fix coding problems that can cause distributed performance issues.
性能和问题分析工具可以帮助您找到并修复代码问题，这些问题可能引起分布式性能问题。
It helps find broken links throughout your site to fix the errors and offers your users a better experience.
它可以帮助找到你整个网站上的断链帮助修复错误，给你的用户提供更好的体验。
Bugs that get through testing and ship to customers are much more expensive to find and fix, and they are also costly to your reputation and ultimately to your business.
故障如果通过了测试并到达了客户，成本将比找到并修复要高得多，而且对您得声誉和最终的业务也有相当大的影响。
Tests are designed to find and fix the bugs.
因此设计测试来查找和修正这些错误。
Some of these users are going to find problems, report them, and even help fix them.
其中有些用户还会发现问题、报告问题甚至是帮助修复问题。
In this scenario, developers run analysis rules to find and fix problems in their component code.
在这个场景中，开发人员执行分析规则在他们的代码组件内发现并修复问题。
Runtime analysis allows developers to pinpoint memory leaks, find and fix application performance bottlenecks, and visualize the execution flow of code and application threads.
运行时分析允许开发者精确地找到内存泄漏，发现并修正应用程序的运行瓶颈，使代码的执行流及应用程序线程可视化。
In typing out code you'll almost always make some mistakes or find mistakes by the author. Figuring out how to fix these mistakes is invaluable.
打出代码时你几乎总会犯一点错误，或者找到作者的什么错误。找出解决这些错误的办法是非常宝贵的经验。
Certainly, if you cannot name or spot the bottlenecks, it's time to find and fix the slowdowns.
当然，如果不能判断出应用程序的瓶颈所在，那么就必须进行查找并加以修复。
Tuning is designed to find problems and fix them.
优化旨在发现问题并修复它们。
They learned that you don't panic when things go wrong and that we can find a way to fix most problems.
他们学到了当事情不对劲时不能惊慌和我们能够找到解决大多数问题的途径。
Whatever it is, find the source of the problem and fix it, instead of just treating the symptom.
不管怎样，找到问题的源头并解决它从而治本，而不是仅仅治标。
With no real system and implementing "quick fix" methods will never help you find leads or customers for your business.
如果没有可行的系统和实行“快速战略”，你将无法找到你的顾客。
When I was debugging, it was taking me just as long to find the offending code as to fix it.
调试时，单是查找有问题的代码所花的时间就与改正错误代码的时间一样长。
Find and fix database problems with constraints, triggers, extents, indexes, and grants Toad utilizes direct Oracle OCI calls for full access to the Oracle API.
定位并修复数据库在约束、触发器、区(extent)和索引上的问题，同时可以让Toad直接利用OracleOCI调用获得对OracleAPI的完全访问。
The suite has already enabled vendors to find and fix numerous bugs in their products.
这个测试套件可以帮助供应商发现和修正产品中的很多bug。
If the application you are testing ever changes, you have to sort through all this code (and all the code in all the other scripts you use to test it) to find and fix problems.
如果您正在测试的应用程序曾经发生变化，您必须将所有这些代码(以及您用来进行测试的所有其它脚本中的代码)进行排序，以发现和修复问题。
With unit testing, you find bugs earlier and fix them more easily than you would without.
通过单元测试，能较早地发现bug并且能比不进行单元测试更容易地修复它们。
In this scenario, developers run analysis rules to find and fix problems in their component code and the development manager runs a standard rule set on the application code base using Build Forge.
在这个场景下，通过使用BuildForge，开发人员在他们的代码或组件中运行分析规则去找到并发现问题，而开发经理可以在基于代码的应用程序系统上运行一组标准的规则集。
Measuring code coverage gives you the information you need to find and fix bugs, producing more robust software for everyone.
测量代码覆盖率使您可以获得寻找并修复bug所需的信息，从而开发出对每个人来说都更健壮的软件。
Alert administrators by email or page when events occur to find and fix problems before they affect the business.
在出现问题时通过电子邮件或页面通知管理员，以便在对业务造成影响之前查找并修复问题。
应用推荐