Most software development is a chaotic activity, often characterized by the phrase "code and fix".
大多数软体开发是一个混乱的开始，常常以一句话代以概括”撰写！
Rather, it focuses on teaching you how to find potential exploits in your code and fix the vulnerabilities.
而是着重于教您如何找到代码中的潜在exploit并修复漏洞。
This article illustrates five common problems in database design, in the PHP code that accesses databases, and how to fix these problems when you see them.
本文说明了数据库设计和访问数据库的PHP代码中出现的五个常见问题，以及在遇到这些问题时如何修复它们。
You can fix this method, too, with the addition of some code to handle users and roles.
这个问题也可以修复，方法是添加一些代码来处理用户和角色。
We needed a better way to test and fix our code.
我们需要一个更好的测试和修复我们代码的方法。
In many cases, updating the use cases and related documentation took longer than the code fix itself.
在许多情况下，更新用例和相关的文档要比修改代码本身花费更多的时间。
The flows within the team break down if a fix is checked-in without updating the bug report, or if there is no link to connect the fix to a particular code stream and build.
如果签入某个修复而没有更新错误报告，或者如果不存在将修复与特定代码流和构建版本联系起来的纽带，则团队中的流就会中断。
Our audit checks for the presence of the Code Red fix, checks for anti-virus software, and extracts its version.
我们的审计检查了“红色代码”修订是否存在，检查了反病毒软件并且抽取出它的版本。
Separating your code in this manner will lead to a highly organized code structure, making it far easier to diagnose and fix any problems that may arise.
以这种方式分离您的代码将产生一个组织良好的代码结构，使得诊断和修复可能出现的问题要容易得多。
The dual approach of studying the code and using debugging tools is the best way to identify and fix problems.
结合研究代码和使用调试工具这两种方法是识别和修正问题的最佳方案。
Many time zones away, a team in Germany performs the testing and produces results for the next day's code change and fix.
相差很多个时区，远在德国的团队执行测试并且为第二天的代码变更和修复出示结果。
In this scenario, developers run analysis rules to find and fix problems in their component code.
在这个场景中，开发人员执行分析规则在他们的代码组件内发现并修复问题。
Building easily maintainable code in this manner will enable you to debug, fix, and extend your code with lower risk.
使用这种方式构建的易维护代码将降低调试、修复和扩展代码所面临的风险。
As a result, the testing team often needs to wait several days to get code changes and fix results.
因此，测试小组经常需要花好几天来等待代码变更和确定的结果。
When the results are generated, you can filter and view them and, if the rule supplies a quick fix feature, you can repair the source code.
当结果被生成的时候，您能够过滤并且查看它们，并且如果该规则提供一个快速修复特性的话，您还能够修复该资源代码。
When developers integrate their code more frequently, they discover problems sooner and fix them before they move downstream.
当开发人员更加频繁地集成代码时，它们会更快地发现问题，并且在向下传之前修正它们。
Willingness for anyone on the project to jump in and fix broken windows regardless of the original author(s) of the code.
项目中的每个人都要自愿参与修复 “破损窗户”，不管代码的原作者是谁。
The left half of that panel shows the code if the quick fix were applied and the right half shows the original code without applying the fix.
如果应用快速修复方案，面板左半边就显示代码，右半边就显示未应用修复方案的原始代码。
Runtime analysis allows developers to pinpoint memory leaks, find and fix application performance bottlenecks, and visualize the execution flow of code and application threads.
运行时分析允许开发者精确地找到内存泄漏，发现并修正应用程序的运行瓶颈，使代码的执行流及应用程序线程可视化。
Imagine that you are working late at night, and you want to temporarily fix someone else's code.
假设您工作到很晚，并且您想要临时修改其他人的代码。
If the component does not behave properly, update or fix the code and then save it.
如果组件没有正确的运行，更新或者修改代码，并保存。
The sample code is a set of classes that illustrate the breadth of the problems that code Review can automatically detect and fix.
样例代码是一组类，说明能够自动检测并修复的问题的宽度。
CSS Tidy is a free, online application that will fix errors and optimize your CSS code.
CSSTidy是免费的在线应用，可修正CSS代码的错误并对其进行优化。
For example, you can integrate Purify with your unit or smoke test suite that developers must run before checking in any code changes and require them to fix any new memory errors reported by Purify.
例如，您可以将Purify与您的单元或者烟雾测试单元整合在一起，这些单元是开发人员必须在报告任何代码变更前必须运行的单元，并需要它们修复Purify所报告的所有新的存储错误。
Measuring code coverage gives you the information you need to find and fix bugs, producing more robust software for everyone.
测量代码覆盖率使您可以获得寻找并修复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.
如果您正在测试的应用程序曾经发生变化，您必须将所有这些代码(以及您用来进行测试的所有其它脚本中的代码)进行排序，以发现和修复问题。
Oftentimes, a bug fix or enhancement spans multiple files and various sections of code in each file.
bug补丁或改进常常涉及多个文件和每个文件中的不同代码段。
Optimized some heavily used CM Server code paths to improve performance, reliability and to fix memory leaks
优化一些经常使用的CM服务器代码路径，以提高性能、可靠性以修复内存泄漏问题
Optimized some heavily used CM Server code paths to improve performance, reliability and to fix memory leaks
优化一些经常使用的CM服务器代码路径，以提高性能、可靠性以修复内存泄漏问题
应用推荐