看看混合的方法，不要犹豫混合不同的技术。
Look at hybrid methods and do not hesitate to mix different techniques.
过好自己的生活，尽量不要制造垃圾：用不同的方法来保护地球。
Live a life and try not to create any rubbish; use different methods to protect the earth.
不要认为你的建议是解决问题的唯一正确方法。
Don't think your suggestion is the only correct way to deal with a situation.
然而，那个方法却有一个放弃声明：不要使用它除非您能确定这个结果。
However, that method comes with a disclaimer: Do not use it unless you are sure of the result.
代码的可读性的第二个关键点，特别在方法级别上，是不要让每个部分做太多的事情。
The second key to readable code is not to have too much of it, especially at the method level.
不要担心——有很多方法都可以解决这个问题。
在研究性学习中，要注意自己需要用到的方法和步骤，同时也不要怯于批判对待它们。
In research studies, notice the methods and procedures, and do not be afraid to criticize them.
当你可以成功地跑很长一段的时候，不要觉得可以你可以丢掉跑步/步行方法。
Once you can successfully run for long stretches, don't feel as if you have to abandon the run/walk method.
当你可以成功地跑很长一段的时候，不要觉得可以你可以丢掉跑步/步行方法。
Onceyou can successfully run for long stretches, don't feel as if you haveto abandon the run/walk method.
随着敏捷过程日渐成熟，作为实践者的我们要忠于敏捷宣言的精神，而不要被敏捷方法诸多变种所定义的形形色色的任务牵着鼻子走，就显得至关重要。
As agile processes mature, it is critical that we as practitioners stay true to the spirit of the agile manifesto, and not be carried away by the tasks defined in the many variants of agile methods.
如果组织需要不同的开发流程，而其组织文化强烈抵制更改，则在尝试改变文化之前，不要尝试采用敏捷方法。
If your organization needs a different development process, yet its organizational culture is strongly against change, don't try to adopt agile methods before trying to change the culture.
不要用这个方法来使用中心存储资产组。
Do not use asset groups that are store-centric with this method.
“‘不要那样去做，要这样做’这种方法并不可行，”他说。
"The 'don't do that, do this' approach doesn't work," he says.
现在，不要误会我：方法指针不是为了侵入代码或者获得对人们现金的引用！
Now, don't get me wrong: Method pointers aren't meant for hacking into code or obtaining references to people's cash!
不论你采用什么方法，不要将冬季衣物放进那些被虫子侵蚀的储存柜- - - - - -除非你打算明年扔到这些衣物。
Whatever you do, don't put winter clothes in storage areas that are bug-addled or dirty-unless you want to throw them out next year.
要避免上述问题，有个出人意料的解决方法：不要让构建代理的网络账号对配置文件有写权限。
A surprisingly easy way to avoid the above problems is to simply not allow the build agent's network account to have write access to the configuration files.
FAB把顺序反过来了，除非听众非常懂技术，否则不要用这种方法。
FAB reverses the order and should not be used unless you have a very technical audience.
错误消息要明确而简洁地解释出错原因、改正方法，不要留给用户去猜测。
The error message clearly and succinctly explains what went wrong, how to fix it, and not leave the user guessing.
不要害怕犯错，因为没有别的方法学会如何生活！
Do not be afraid of making mistakes, for there is no other way of learning how to live!
与朋友谈论：如果你手头没有电脑，那就不要忘了使用模拟的方法——打电话或者喝咖啡的时候告诉他/她你看到的好的文章。
Talking to Friends: If you don’t have a computer handy, then don’t forget about the analog approach - call a friend or tell him or her over coffee about a great blog post you read.
应对方法：不要给招聘经理任何理由来怀疑你对细节问题的注意和专业性。
Takeaway tip: Don't give hiring managers any reason to question your professionalism or attention to detail.
尤辛表示，方法很简单：不要去想竞争会带来什么，而是从竞争对手的角度进行思考。
This particular trick is simple: don't think what the competition would do, think like competitors.
请不要使用该方法存储任何不能丢失的敏感数据，比如icbm启动代码或信用卡号。
Don't use this technique to store anything that's too sensitive to lose, like ICBM launch codes or credit card Numbers.
一定要坚持这些HTTP方法的正规用法，不要偏离规范。
It is important to stick to the classical usage of these HTTP methods and not try to deviate from them.
求极大值时，最好不要用导数的方法，因为它不存在。
If you are looking for the maximum, you better not just look at the derivative because you won't find it that way.
再次强调一下，Seam应用入门最简单的方法就是，不要担心这些配置文件，只需要从已有的应用模板做起。
Again, the simplest way to start your Seam application is not to worry about those configuration files at all and start from a ready-made application template.
不要忘记在handle()方法签名中修改MessageContext的变量名称。
Don't forget to modify the variable name for MessageContext in the handle() method signature.
在实现中不要使用安全方法(如GET和HEAD)进行不安全的操作(如，写数据)，这点非常重要。
It's important that implementations do not use safe methods e.g. GET and HEAD to perform unsafe operations e.g.
建议不要将此方法用于非ejb3环境，因为可能无法正确管理所创建的任何EntityManager。
This approach is not recommended for a non-EJB 3 environment, because any EntityManagers created might not be properly managed.
请不要期望任何会话bean方法的输出能反映因运行其它方法而造成的数据变化。
Do not expect the output of any of the session bean methods to reflect data changes from running other methods.
应用推荐