Many computer game and small-time software companies still use a fairly loose development model usually big-bang or code-and-fix.
很多电脑游戏和小规模的软件公司仍然使用简单松散的开发模型，比如“大爆炸模型”，“编码与修复模型”。
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.
这个问题也可以修复，方法是添加一些代码来处理用户和角色。
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.
以这种方式分离您的代码将产生一个组织良好的代码结构，使得诊断和修复可能出现的问题要容易得多。
In many cases, updating the use cases and related documentation took longer than the code fix itself.
在许多情况下，更新用例和相关的文档要比修改代码本身花费更多的时间。
Building easily maintainable code in this manner will enable you to debug, fix, and extend your code with lower risk.
使用这种方式构建的易维护代码将降低调试、修复和扩展代码所面临的风险。
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.
当结果被生成的时候，您能够过滤并且查看它们，并且如果该规则提供一个快速修复特性的话，您还能够修复该资源代码。
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.
如果签入某个修复而没有更新错误报告，或者如果不存在将修复与特定代码流和构建版本联系起来的纽带，则团队中的流就会中断。
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.
如果应用快速修复方案，面板左半边就显示代码，右半边就显示未应用修复方案的原始代码。
Many time zones away, a team in Germany performs the testing and produces results for the next day's code change and fix.
相差很多个时区，远在德国的团队执行测试并且为第二天的代码变更和修复出示结果。
The dual approach of studying the code and using debugging tools is the best way to identify and fix problems.
结合研究代码和使用调试工具这两种方法是识别和修正问题的最佳方案。
Willingness for anyone on the project to jump in and fix broken windows regardless of the original author(s) of the code.
项目中的每个人都要自愿参与修复 “破损窗户”，不管代码的原作者是谁。
Bugs in untested code will "escape" into release, and they will be much more costly to find and fix.
没有测试到的错误将会“逃离”进入释放，找到并修复它们的成本将十分昂贵。
In this scenario, developers run analysis rules to find and fix problems in their component code.
在这个场景中，开发人员执行分析规则在他们的代码组件内发现并修复问题。
The source code is available, so that you can study the software, adapt it to your needs, fix bugs, and release versions with new features.
它们的源代码是对外公布的，方便你从中学习，根据自己的需要进行改造，修补存在的漏洞，并发布具有新特性的版本。
We explored how the situations arose in the application, and then saw how to best fix the problematic code to make testing possible.
我们还介绍了这些情况是如何出现在应用程序中的，然后介绍了如何恰当地修复这些问题代码来便于进行测试。
As a result, the testing team often needs to wait several days to get code changes and fix results.
因此，测试小组经常需要花好几天来等待代码变更和确定的结果。
Runtime analysis allows developers to pinpoint memory leaks, find and fix application performance bottlenecks, and visualize the execution flow of code and application threads.
运行时分析允许开发者精确地找到内存泄漏，发现并修正应用程序的运行瓶颈，使代码的执行流及应用程序线程可视化。
And then you have a little problem, and you go and you fix the little problem, because it's code, and you have an editor, and you edit it.
然后有些小问题，接下来你过来解决这些小问题，因为它是代码，而你有编辑器，你能修改它。
When developers integrate their code more frequently, they discover problems sooner and fix them before they move downstream.
当开发人员更加频繁地集成代码时，它们会更快地发现问题，并且在向下传之前修正它们。
If the component does not behave properly, update or fix the code and then save it.
如果组件没有正确的运行，更新或者修改代码，并保存。
Given that everyone on the team will be going through the "write a test, fix the code, refactor" cycle frequently, it's essential that you can both write and run tests efficiently.
假使项目中的每一个人都在周而复始地重复“写测试，修改代码，重构”，当然有必要使你的测试工作更加有效。
Although generic types can be a powerful weapon for producing robust code, we've shown how their misuse can lead to code that is not only less robust but also extraordinarily hard to diagnose and fix.
尽管泛型类型是制作健壮代码的强大武器，但我们已经演示了误用它们会使代码不再健壮而且极难诊断和修正。
When errors are found, defects are logged and source code is modified to fix the defect.
当找到错误后，缺陷就会被记录到日志，源代码也会被修改，从而修复这个缺陷。
Imagine that you are working late at night, and you want to temporarily fix someone else's code.
假设您工作到很晚，并且您想要临时修改其他人的代码。
The sample code is a set of classes that illustrate the breadth of the problems that code Review can automatically detect and fix.
样例代码是一组类，说明能够自动检测并修复的问题的宽度。
It tells the developer that this rule will be a severity 1 within the next 6-12 months, so they should probably fix it now before they find themselves under a deadline and unable to build their code.
它告诉开发人员，在下一个6 - 12月内，此等级的问题会上升到第一等级，因此在此之前应该将这些问题解决掉。
It tells the developer that this rule will be a severity 1 within the next 6-12 months, so they should probably fix it now before they find themselves under a deadline and unable to build their code.
它告诉开发人员，在下一个6 - 12月内，此等级的问题会上升到第一等级，因此在此之前应该将这些问题解决掉。
应用推荐