Practicing on a Computer
只在电脑上练习

If you were training for a serious bike race in the mountains, would you practice only by bik-ing on the streets? I hope not The air is different The terrain is different Yeah, I bet you’dpractice in the mountains
如果你正在准备山地自行车比赛，你会在马路上练习吗？我想肯定不会吧。因为两者的气温，地形有很大的差异。所以我打赌你会在山地上练习！

Using a compiler to practice interview questions is like this - and you’ve basically been bikingon the streets your entire life Put away the compiler and get out the old pen and paper Usea compiler only to verify your solutions
那么用编译器来帮你准备面试，就像在马路上练习山地自行车一样。还是老老实实的拿出尘封已久的笔和纸来练习吧。编译器还是留到最后验证答案的时候用。

Not Rehearsing Behavioral Questions
不准备行为面试

Many candidates spend all their time prepping for technical questions and overlook the behavioral questions Guess what? Your interviewer is judging those too! And, not only that- your performance on behavioral questions might bias your interviewer’s perception of your technical performance Behavioral prep is relatively easy and well-worth your time Lookingover your projects and positions and think of the key stories Rehearse the stories Seepg 29 for more details
很多应聘者花了大量的时间准备技术问题，忽视了行为问题。知道吗嘛，面试官一样看重行为问题。而你行为问题方面的表现会影响面试官对你问答技术问题的评价。况且准备行为问题也非常的简单，性价比很高。浏览你简历上涉及的项目和职位信息，总结下每个项中的重要信息。具体的方法在之前的章节已经介绍过了。

Not Doing a Mock Interview
不做模拟面试

Imagine you’re preparing for a big speech Your whole school, or company, or whatever willbe there Your future depends on this And all you do to prepare is read the speech to your-self Silently In your head Crazy, right? Not doing a mock interview to prepare for your real interview is just like this If you’re anengineer, you must know other engineers Grab a buddy and ask him/her to do a mockinterview for you You can even return the favor!
假想下你正准备一个演讲，全学校或者全公司的都会来听，不管怎么说这次演讲对你至关重要。如果你只是每次都对着自己默念来准备的话，是不是觉得很傻？不做模拟面试就和这件事情一样傻。随便拉一个同事过来，让他给你模拟面试一次。你们也可以相互面，礼尚往来嘛。

Trying to Memorize Solutions
背答案

Quality beats quantity Try to struggle through and solve questions yourself; don’t flip di-rectly to the solutions when you get stuck Memorizing how to solve specific problem isn’tgoing to help you much in an interview Real preparation is about learning how to approachnew problems
质量胜于数量。通过自己的努力去解题；不要一碰到不会的就直接翻答案。直接背答案的话在面试的时候对你帮助真不太大。准备面试的目的不是去背答案，而是学会解决新问题的方法。

Talking Too Much
话太多

I can’t tell you how many times I’ve asked candidates a simple question like “what was thehardest bug on Project Pod?”, only to have them ramble on and on about things I don’t understand Five minutes later, when they finally come up for air, I’ve learned nothing - exceptthat they’re a poor communicator When asked a question, break your answer into three parts (Situation / Action / Response, Issue 1 / Issue 2 / Issue 3, etc) and speak for just a couple sentences about each If I want more details, I’ll ask!
问了应聘者一个简单的问题，例如“这个项目中最棘手的bug是什么？”，结果他唧唧歪歪唧唧歪歪半天也没有说到重点，我却雾水什么都没听懂，最后只能得出结论：这个人的沟通能力有问题。这样的情况都不知道遇到多少次了。在面试时回答问题前心中最好能有个提纲(情形-行动-结果或者1,2,3点的形式)，每点说一两句就够了。如果面试官想知道细节，他们自己会问的。

Talking Too Little
话太少

Psst - let me tell you a secret: I don’t know what’s going on in your head So if you aren’t talk-ing, I don’t know what you’re thinking If you don’t talk for a long time, I’ll assume that youaren’t making any progress Speak up often, and try to talk your way through a solution This shows your interviewer that you’re tackling the problem and aren’t stuck And it lets them guide you when you get off-track, helping you get to the answer faster And it shows yourawesome communication skills What’s not to love?
嗯，告诉你，我是永远猜不到你脑袋里面在想什么的。在面试的时候如果你不开口说话，我就不知道你在想什么。如果你一直不说话，我就会简单认为你卡壳了。多开口说话，在解题过程中就多讲讲你的想法。这样面试官才能知道你是在解题而不是发呆。而且如果你的思路有问题，面试官还能根据你说的给你些提示。此外多和面试官交流，他们会认为你的沟通能力还不错，何乐而不为呢？

Rushing
急匆匆

Coding is not a race, and neither is interviewing Take your time in a coding problem - don’trush! Rushing leads to mistakes, and reveals you to be careless Go slowly and methodically,testing often and thinking through the problem thoroughly You’ll finish the problem in lesstime in the end, and with fewer mistakes
写代码不是比赛，面试也一样不是。面试写代码的时候千万不要匆匆忙忙的。写的太快容易出错，错误会让面试官觉得你粗心大意。慢慢写代码，系统的测试自己写的代码，吃透问题。慢慢写最后会让你完成得更快，而错误更少。

Not Debugging
不调试

Would you ever write code and not run it or test it? I would hope not! So why do that in aninterview? When you finish writing code in an interview, “run” (or walk through) the code totest it Or, on more complicated problems, test the code while writing it
你平时写完代码就直接完事的吗？我想肯定不是吧。那面试的时候写的代码也一样对待吧。面试的时候虽然没有电脑让你“Run”，但是过一遍代码。如果代码复杂一些的话，最好能设计一两个测试用例来，边写边测。

Sloppy Coding
烂代码

Did you know that you can write bug-free code while still doing horribly on a coding question? It’s true! Duplicated code, messy data structures (i e , lack of object oriented design),etc Bad, bad, bad! When you write code, imagine you’re writing for real-world maintain-ability Break code into sub-routines, and design data structures to link appropriate data
你觉得你在解决一个难题的时候，能不能写出没有错误代码吗？肯定不行吧！重复代码，混乱的数据结构，等等不好的代码习惯。在面试的时候就假设自己真正的在开发。什么提取含函数啦，设计模式啦能用上的就别不好意思用！

Giving Up
放弃

Have you ever taken a computer adaptive test? These are tests that give you harder ques-tions the better you do Take it from me - they’re not fun Regardless of how well you’re actually doing, you suddenly find yourself stumbling through problems Yikes!
你做过这样的测试吗？测试题的难度根据你的表现一步一步提高。告诉你这样的测试没有意思的。别以为你自己平时有多厉害，你也会突然卡在一个难题上的。

Interviewing is sort of like this If you whiz through the easy problems, you’re going to getmore and harder problems Or, the questions might have just started out hard to begin with!Either way, struggling on a question does not mean that you’re doing badly So Don’t give up or get discouraged You’re doing great!
面试也是这样的。如果你秒了简单题，那么接下来迎接你的就是难题了。还有可能你上来就碰到一个巨难的问题。不管什么样情况，努力的解题并不说明你做的不好。所以千万别在做题的时候气馁和放弃。你做的很好！