These errors nearly always indicate sloppy programming. So if it's your code, you should clean them up anyway.
这些错误几乎总是表明编程草率。所以如果是您的代码，无论如何都应该清除这些错误。
What happens if you do have tabs in your code?
如果代码中有制表符，会发生什么情况？
Ensure that your code runs fast.
确保您的代码快速运行。
Invoke the markup handler in your code.
如何在代码中使用markup处理程序？
Compiles, tests, and packages your code.
编译、测试并打包代码。
Refactor your code and automate your tests.
重构代码并自动化测试。
This wrapper also makes your code more portable.
这个包装器也会使应用程序代码的可移植性更好。
Handling errors properly makes your code more robust.
适当地处理错误会使代码更加健壮。
Now, back to what I promised, making your code rock-solid.
现在，回到我所承诺的问题上，使您的代码健壮起来。
To get your code to the server, there's integrated FTP.
要把代码放到服务器上，有集成FTP可以使用。
Errors in PHP point you right to the error in your code.
PHP中的错误会指向代码中的错误。
Look for ways to simplify your code right from the outset.
从一开始就要寻求使得代码简洁的方法。
You should start debugging by placing breakpoints in your code.
您应当从在代码中放置断点开始进行调试。
Adding metadata to your code also increases its complexity.
在代码中加入元数据还会增加代码的复杂性。
Without tests, changing your code would be a guessing game.
如果不进行测试，修改代码就会象猜谜一样。
Practicalities: DRY 'ing up your code and best practices (16:09).
实用性：DRY你的代码，并应用到实践中去(16：09)。
This way your code isn't tied to any particular XML handling API.
这样你的代码就不依赖任何特殊的XML处理API了。
Develop a habit of formatting your code comments consistently.
找到一种属于自己的注释格式。
Merge down the latest from the work branch, and check in your code.
从工作分支中取得并合并最新的代码，然后检入你的代码。
Thinking like a cracker is the next step in defending your code.
以一个攻击者的角度进行思考是防护代码的下一个步骤。
When a new variation of an abstraction comes up, your code still works.
当提出了抽象的一个新实现时，你的代码仍然可以正常运行。
This reduces the requirement to test the spawning process in your code.
这能减少在代码中测试生成进程的需要。
This documentation makes it easier for others to put your code into context.
该文档使其他人更容易地将您的代码放入上下文中。
Bitmaps are traditionally represented inside your code by an array of chars.
传统上，位图在代码内由一个字符数组表示。
In strong code ownership, there's my code and your code. I can't change your code.
在强代码所有权中，严格区分我的代码和你的代码，我不能改动你的代码。
But in general, the choice of variable name is a great way of commenting your code.
但是通常来说，变量名称的选择，是评论你的代码的，一个重要方式。
So, the only way in which we know that your code works is through the user interface.
所以，我们判断你的代码是不是正确的唯一方式，就是通过用户界面。
Do that and suddenly your code is 80 percent generics, annotations, and enumerations.
如果这样做，那么您的代码就会突然之间有80%是泛型、标注和枚举。
The new Call Hierarchy window helps you analyze your code and navigate within it.
调用层次结构窗口可以帮助你分析代码，并在该窗口内导航。
Obviously, this leads to false positives and portions of your code left untested.
显然，这将导致测试成功的假象，而且还会使得部分代码得不到测试。
应用推荐