mcu比较器技巧和诀窍_如何准备技术面试-技巧和窍门，以帮助您表现最好

mcu比较器技巧和诀窍

Ah, the coding interview.

嗯，编码面试。

"Dread it. Run from it. Destiny arrives all the same."    - Thanos 2018

“恐惧。逃避它。命运同样到达。” -Thanos 2018

Ok, maybe that's a little dramatic, but I don't know anyone who is thrilled about going through the interview process. The job search/interview process is exhausting at best and many other things at worst.

好的，也许有点戏剧性，但是我不知道有人对采访过程感到兴奋。 求职/面试过程充其量是精疲力尽，而最糟糕的是很多其他事情。

Many people study up on tricks and tactics for an interview (and I'll give you a few of those too), but most people don't think about their mindset going in to the interview.

很多人都在研究面试的技巧和策略(我也会给你一些)，但是大多数人并没有考虑面试的思路 。

Your mindset sets the tone of how you're going to view and shape your situation. Go in with the right mindset and you'll be able to understand and navigate anything that is thrown at you. Enter with a scattered or timid mind and you'll find yourself rocked about and battered.

您的心态定下了如何查看和塑造情况的基调。 以正确的心态进入，您将能够理解和浏览扔给您的任何东西。 带着分散或胆怯的思想进入，您会发现自己被震撼了。

你也是面试官 (You are also the interviewer)

One thing most people often forget is you are also the interviewer.

大多数人经常忘记的一件事是您也是面试官。

Yes, are you being interviewed at this company, but you are also interviewing the company to see if they are a good fit for you.

是的，您正在这家公司接受面试，但是您也在面试该公司，以了解它们是否适合您。

What are this company's values? What is their work ethic like? What do the people value?

这家公司的价值观是什么？ 他们的职业道德是怎样的？ 人们看重什么？

Passing the interview is important, but do you want to work at this company if you do pass?

通过面试很重要，但是如果通过，您是否想在这家公司工作？

Sometimes we just need a job—any job—and so I don't want to minimize just getting the job. But if you can, take a step back and think how this job will impact your career in the long-term. Saying yes to a job is saying no to a dozen others—you're paying a large opportunity cost by saying yes.

有时我们只需要一份工作-任何工作-因此我不想将获得工作的机会降到最低。 但是，如果可以的话，请退后一步，考虑一下这项工作将长期影响您的职业。 对一项工作说“是”就等于对其他许多人说“不” —您说“是”会付出很大的机会成本。

So that's the first thing to remember: this isn't a one-way power dynamic. It may feel like it at times, but you have some control here, and you have options. This is empowering.

这是要记住的第一件事：这不是单向动力动态。 有时可能会感觉很像，但是您在这里有一些控制权，并且可以选择。 这是授权。

面试类型 (Types of interviews)

Ok, so we are also evaluating the company based on the people we interact with in the interview process, so what do we do with that information?

好的，所以我们也在面试过程中基于与我们互动的人员来评估公司，那么我们该如何处理这些信息？

Well, there are a few different types of technical interviews. These interview types tell us a lot about the mindset of the company and what it is like to work there. I break down the different types like this:

好吧，有几种不同类型的技术面试。 这些面试类型告诉我们很多关于公司的心态以及在那工作的感觉。 我将不同的类型分解如下：

• Whiteboarding
  白板
• Code challenge (computer science questions or algorithms)
  代码挑战(计算机科学问题或算法)
• Code challenge (reasonable coding problem)
  代码挑战(合理的编码问题)
• Take home project
  带回家的项目

可怕的白板 (The dreaded whiteboard)

Some of the first interview exercises the tech industry adopted were whiteboard exercises. You'd be given a task, and asked to write the code on the whiteboard. Generally, this approach is looked down upon and is being done away with in the tech industry today, but there are still many companies that employ this practice.

科技行业采用的一些首次面试练习是白板练习。 您将被赋予一项任务，并被要求在白板上编写代码。 通常，这种方法在当今的技术行业中被人们所忽视，并且已经被淘汰，但是仍然有许多公司采用这种方法。

It's not that coding on a whiteboard is bad in and of itself—but that a whiteboard is so far removed from the work we actually do as programmers who work on computers every day. The whiteboard is clumsy to write on, edit on, and it doesn't give you any feedback—there's no autocomplete, no syntax highlighting, and you can't pop over to Google to look up the standard library's references.

这不是一个编码白板上是坏的 -但它本身是一个白板是迄今为止从加工除去我们实际上每天做程序员的计算机上谁工作 。 白板很难编写，编辑，也无法给您任何反馈-没有自动完成功能，没有语法突出显示，您无法跳到Google来查找标准库的引用。

On top of that, many places who employ whiteboard interviewing also ask a certain set of interview questions that, frankly, are worthless to 99% of programming jobs out there. These are the dreaded computer science algorithms: reversing a binary tree, finding the shortest path in a graph, etc.

最重要的是，许多使用白板面试的地方还提出了一些面试问题，坦率地说，这些问题对99％的编程工作毫无价值。 这些是可怕的计算机科学算法：反转二叉树，在图形中找到最短路径等。

The problem with these questions is they just don't come up in real life as a programmer. If you're interviewing at Amazon or Facebook, sure, maybe they have some value there, but the majority of people will never face this problem in their career. And if they do, they'll just use some package or library that has already implemented that functionality.

这些问题的问题在于， 它们在现实生活中根本不是程序员。 当然，如果您正在亚马逊或Facebook面试，也许他们在那里有价值，但是大多数人在职业生涯中永远不会遇到这个问题。 如果这样做，他们将只使用一些已经实现该功能的软件包或库。

So what can we do about whiteboards? Well, here's what I would do: do your best, use the tips and tricks outlined below, and seriously evaluate if this interview practice is a symptom of a larger mentality issue within the company.

那么，我们该如何处理白板？ 好吧，这就是我要做的事情：尽力而为，使用下面列出的提示和技巧，并认真评估这种面试实践是否是公司内部更大的心理问题的征兆。

代码挑战 (Code challenges)

If you're lucky enough to dodge the whiteboard, most places will (and probably should) ask you to do some sort of code challenge. Again this may seem like a one-way power dynamic, but this code challenge is actually good for you. This is where you get to shine and show your technical competence, and in my experience this drastically affects your negotiation power when it comes to job rank and pay.

如果您很幸运地躲过了白板，大多数地方都会(也许应该)要求您进行某种代码挑战。 同样，这似乎是单向动力动态，但是此代码挑战实际上对您有好处。 在这里，您将大放异彩并展现出自己的技术能力，而根据我的经验，这在职位等级和薪资方面将极大地影响您的谈判能力。

Before we get into the specific tips, we should also be aware that just because you've dodged the whiteboard doesn't mean that you won't still get the computer science algorithm question here—just on a computer. If that's the case, just take a deep breath and use the tips and tricks below. You'll get through it.

在介绍具体技巧之前，我们还应该意识到，仅仅因为您躲过了白板并不意味着您仍然不会在这里遇到计算机科学算法的问题，而只是在计算机上。 如果是这种情况，请深呼吸，并使用下面的提示和技巧。 您会通过它。

In you're lucky enough to dodge the whiteboard and the CS question you've probably been presented with a reasonable coding challenge. To me these are questions like:

在您很幸运的情况下，您可以躲避白板和 CS问题，您可能会遇到一个合理的编码挑战。 对我来说，这些是类似的问题：

Write a function that takes in a number of cents (USD) as an integer less than or equal to 100, and prints out the least amount of coins needed to represent it.

编写一个函数，该函数以美分(USD)为小于或等于100的整数，并输出表示该数字所需的最少数量的硬币。

50 => 2 quarters

50 => 2个季度

11 => 1 dime and 1 penny

11 => 1角钱和1便士

I've also received questions that seem like CS questions but are really not that bad. For example, "implement a doubly-linked list." At first glance, this seems like a CS problem due to the "doubly-linked list" part, but what the interviewer was actually wanting was code that implemented the same behavior as a doubly-linked list—I wasn't using pointers and addressing objects in memory—just mimicking the same behavior. In that case it ended up being a fairly simple challenge.

我还收到了一些看起来像CS问题的问题，但实际上还不错。 例如，“实现双向链接列表”。 乍一看，由于“双向链接列表”部分，这似乎是一个CS问题，但访问员实际上想要的是实现与双向链接列表相同行为的代码-我没有使用指针和寻址内存中的对象-只是模仿相同的行为。 在那种情况下，这最终是一个相当简单的挑战。

And that brings me to my first tip:

这就是我的第一个秘诀：

提示1：提出澄清问题 (Tip 1: Ask clarifying questions)

In the doubly-linked list challenge I was given a blank Ruby file (I was interviewing for a Ruby job), and a blank test suite. Something like this:

在双向链表挑战中，我得到了一个空白的Ruby文件(我正在面试Ruby的工作)和一个空白的测试套件。 像这样：

class DoublyLinkedList
end

(If you're not familiar with Ruby—don't worry. The code here will be simple to understand. It's just here to illustrate the overall points.)

(如果您不熟悉Ruby，请放心。这里的代码很容易理解。这里只是为了说明要点。)

So, a doubly linked list eh? Maybe you know what that is, or maybe you don't. If you don't: ask questions. This is the first pitfall to avoid. If you don't understand the problem or what they are asking for, keep asking questions until you do.

那么，双向链表是吗？ 也许您知道那是什么，或者也许您不知道。 如果您不这样做： 问问题。 这是要避免的第一个陷阱。 如果您不了解问题或他们的要求，请继续提出问题，直到您明白为止。

I've seen interviewees go down the wrong rabbit trail and the interviewer just let them—all the while silently going to fail them. While I don't agree with this practice, make sure you're working the right problem.

我已经看到受访者走错了路，而采访者只是让他们-一直在默默地使他们失败。 虽然我不同意这种做法，但请确保您正在解决正确的问题。

I do come from a computer science background, so I knew a doubly-linked list means a list that has a pointer to a head and a tail node—where each node also points to its next and previous node.

我确实来自计算机科学背景，所以我知道一个双向链接列表意味着一个列表，该列表具有指向head节点和tail节点的指针，其中每个节点还指向其next和previous节点。

Now even though I knew that, what did I do? I said that out loud and asked if that was correct. Even though I thought I knew what to do, I made absolute sure I did.

现在，即使我知道该怎么办？ 我大声地说，问那是否正确。 即使我以为自己知道该怎么做，但我绝对确定自己做了。

Once you think you understand the problem, restate your understanding the interviewer so they can correct or guide you.

一旦您认为自己理解了问题，请重申对面试官的理解，以便他们可以纠正或指导您。

The next thing I did was ask another question: "Can I use an array for the nodes?" And I typed out something like this:

我要做的第二件事是问另一个问题： “我可以为节点使用数组吗？” 我输入了以下内容：

class DoublyLinkedList
  def initialize
    @nodes = []
  end
end

(If you're not familiar with Ruby this is just an initializer or constructor where I make a new variable called @nodes set to an empty array.)

(如果您不熟悉Ruby，那么这只是一个初始化程序或构造函数，我在其中将名为@nodes的新变量设置为一个空数组。)

But, the interviewer told me, no, I couldn't do that—which makes sense. If I had used an array it would have defeated the whole purpose of the exercise which is building out the fake "pointers" between the nodes.

但是，面试官告诉我，不，我不能那样做-这是有道理的。 如果我使用了一个数组，那将使练习的全部目的无效，后者是在节点之间建立伪造的“指针”。

And boy, am I glad I asked. I didn't want to take the chance that the interviewer would let me use the array, and then fail me.

和男孩，我很高兴我问了。 我不想抓住面试官让我使用阵列，然后让我失望的机会。

So no array—well what do I do now? Here's tip #2:

所以没有阵列-那么我现在该怎么办？ 这里的提示2：

提示2：硬编码->哑->更好 (Tip 2: Hardcoded -> Dumb -> Better)

When you face a coding challenge, work the problem in the following order: hardcoded -> dumb -> better -> even better (if time allows).

当您遇到编码挑战时，请按以下顺序处理问题： 硬编码->哑->更好->更好(如果时间允许)。

In my experience being interviewed and interviewing other developers, I find that most people try to do too much all at once.

根据我采访和采访其他开发人员的经验，我发现大多数人试图一次做太多事情。

When you do too much at once it's easy to make mistakes (that you won't catch due to having InterviewBrain™). So start simple—the simplest you can in fact—hardcoded—and work your way up.

当您一次执行过多操作时，很容易出错(由于拥有InterviewBrain™，您不会被抓住)。 因此，从简单(实际上是最简单的事情)开始就进行硬编码，然后逐步进行。

So I have a blank Ruby class, how can I hardcode something to progress forward? I looked at my empty test suite and saw that there was a function called head that returned the first node in the list, so let's try that:

因此，我有一个空白的Ruby类，如何对某些内容进行硬编码以继续前进？ 我看着空的测试套件，发现有一个名为head的函数返回了列表中的第一个节点，因此让我们尝试一下：

class DoublyLinkedList
  def head
    'A'
  end
end

I made a head function, and hardcoded the capital letter "A" as a string, and I ran that test. It passed.

我做了一个head函数，并将大写字母“ A”硬编码为字符串，然后运行了该测试。 通过了

Is this super simple? Is it too obvious? Yes! But this code does two very important things:

这超级简单吗？ 太明显了吗？ 是! 但是这段代码做了两件非常重要的事情：

• It allows me to run the tests and test that my setup works (eliminating any silly or syntax errors)
  它允许我运行测试并测试我的设置是否有效(消除了任何愚蠢或语法错误)

• It gets me a quick win—which boosts my confidence

  它使我快速获胜，这增强了我的信心

There are countless interviews I've seen where someone makes a small mistake right at the beginning, gets flustered, and then spends the majority of the interview trying to recover and fix whatever is wrong.

我见过无数次面试，其中有些人在一开始就犯了一个小错误，然后心慌意乱，然后花了大部分面试试图恢复并解决错误。

Don't underestimate the value of quick wins for your confidence. Stacking up small wins will propel you through the interview.

不要低估快速获胜的价值，这对您有信心。 积累一些小的胜利将推动您通过面试。

Ok, we have a hardcoded string 'A'. Now how do we make that into a dumb solution? Well, how about making that letter "A" into a hash (or map)?

好的，我们有一个硬编码的字符串'A' 。 现在我们如何将其变成一个愚蠢的解决方案？ 好吧，如何将字母“ A”制成哈希(或映射)？

class DoublyLinkedList
  def head
    { value: 'A' }
  end
end

That's a little better. Now instead of a one character string our "node" is represented as hash with a value property. We've gone from hardcoded to dumb. Now how can we make it better? Well, how about we introduce our head pointer in the list?

好一点。 现在，我们的“节点”由一个带有value属性的哈希表示，而不是一个字符串。 我们已经从硬编码变成了傻瓜。 现在我们如何才能使其更好？ 好吧，我们如何在列表中引入head指针呢？

class DoublyLinkedList
  def initialize
    @head = { value: 'A' }
  end
  
  def head
    @head
  end
end

What did we change here? Here we add back our initializer and create a new variable called @head, and we use that new variable in our head function. This is beginning to look like some real code.

我们在这里改变了什么？ 在这里，我们重新添加初始化程序并创建一个名为@head的新变量，然后在head函数中使用该新变量。 这开始看起来像是一些真实的代码。

Now this approach may seem really silly, but I promise you, it works. Each of these changes are made in seconds of small, iterative coding, and they stack up to produce a working implementation in short time.

现在，这种方法看起来确实很愚蠢，但是我向您保证， 它可行。 这些更改中的每一个都是在几秒钟的小规模迭代编码中完成的，并且它们叠加起来可以在很短的时间内产生有效的实现。

If you're thinking this approach will seem odd to a potential interviewer, here's the next tip, and this one is very important:

如果您认为这种方法对潜在的面试官来说似乎很奇怪，那么这里是下一个提示， 这个提示非常重要：

提示3：交谈。 响亮地。 (Tip 3: Talk. Out loud.)

The entire time you're doing a coding challenge you should be talking—out loud.

在进行编码挑战的整个过程中，您都应该大声讲话。

Say everything you're thinking—everything.

说出您正在考虑的所有内容。

(Well, everything programming related.)

(嗯，所有与编程有关的东西。)

Here's the thing: getting to a correct solution is important yes, but equally if not more important is showing your thought process. The interviewer wants to know how you think—how you solve problems. You can do this by sharing everything you're thinking out loud.

事情是这样：寻求正确的解决方案很重要，是的，但是如果不是更重要的话，同样也可以显示您的思维过程。 面试官想知道您的想法，即您如何解决问题。 您可以通过大声分享正在考虑的一切来做到这一点。

Every interviewer has at some point been an interviewee—they know about InterviewBrain™ and that even simple things can become difficult in an interview. Good interviewers don't care that you get the solution 100% right—they just want to know that you possess good critical thinking abilities. The only way to make these internal thoughts visible is to say them out loud.

每个访调员在某个时候都是被访者，他们了解InterviewBrain™，即使简单的事情也很难在面试中变得困难。 优秀的面试官不在乎您能否正确地获得解决方案，而只是想知道您拥有良好的批判性思维能力。 使这些内部思想可见的唯一方法是大声说出来。

If you've never done this before, you might want to practice it because it's vital for nailing the interview.

如果您以前从未做过此事，则可能要练习一下，因为这对于钉住面试至关重要。

To give you some practical examples, here are some things I say every single time I'm interviewed:

为了给您一些实际的例子，以下是我每次面试时都会说的一些话：

"Ok, let's just hardcode this value and make sure our setup works."

“好吧，我们只对这个值进行硬编码，并确保我们的设置有效。”

"Let's get a dumb version of this working first and make it better."

“让我们先弄个傻瓜版本，使它更好。”

"I'll do it like this for now, and if we have time come back and do ."

“我现在就这样做，如果我们有时间再回来做。”

"Ok so we need a function that takes in an array, does X, and returns ."

“好吧，所以我们需要一个接受数组，X并返回的函数。”

In some scenarios, these interviews can start to feel like pair programming sessions.

在某些情况下，这些采访可能开始让人感觉像是结对编程会议。

Ok, so we're saying things out loud. But sometimes we make a mistake or we get stuck. We've been speaking our thought process out loud, but now we may need to shift and investigate a potential issue or error.

好的，所以我们要大声说出来。 但是有时候我们会犯错或者陷入困境。 我们一直在大声说出自己的思维过程，但现在我们可能需要转移并调查潜在的问题或错误。

Here's an important tip for this:

这是一个重要提示：

提示4：保持逻辑流程 (Tip 4: Stay in a logical flow)

Now I'll admit: this one can be hard at times.

现在，我承认：这有时可能很难。

If you're in an interview and there's a problem or error with your code, your brain desperately wants to figure out what is wrong—but don't be too desperate that you begin thrashing your code or your thought process.

如果您正在面试中，并且代码存在问题或错误，那么您的大脑会拼命地想找出问题所在，但不要太着急以至于您开始乱动代码或思考过程。

You see, just like the interviewer wants to see how you break down a problem, they also want to see how you debug a problem. This is equally as important as explaining your thought process. Try your best to stay in a logical flow and avoid thrashing the code or your ideas.

您会看到，就像面试官想看到您如何解决问题一样，他们也想看到您如何调试问题。 这与解释您的思维过程同样重要。 尽最大努力保持逻辑流程，避免破坏代码或想法。

如果一切顺利 (If it's going well)

So the challenge is going well, and you're knocking out the problem and all of the easy stuff.

因此，挑战进行得很顺利，您正在解决问题以及所有简单的问题。

What now? How do you go from passed to crushed it?

现在怎么办？ 您如何从传递到粉碎呢？

This is an extremely important part of the interview, because this is where you get the majority of your leverage for job level and compensation negotiation. And the tip is:

这是面试中极为重要的部分，因为这是您获得工作水平和薪酬谈判的大部分杠杆的地方。 提示是：

提示5：显示您所知道的 (Tip 5: Show what you know)

You're working the challenge, you're talking out loud, and you're doing well. The next thing you need to be looking for are opportunities to show your knowledge and expertise.

您正在应对挑战，正在大声说出来，并且您做得不错。 您需要寻找的下一件事是展示您的知识和专业知识的机会。

Is this the place in the code where you might send an email? Mention that it should be done in a background worker instead (you probably won't even have to implement it).

这是代码中您可以发送电子邮件的地方吗？ 提到应该在后台工作人员中完成它(您可能甚至不必实现它)。

Are you working on validation logic in a model? Talk about how you would also add database constraints to ensure data integrity. What indexes would you add? How would you roll out the migrations to prevent downtime?

您是否正在研究模型中的验证逻辑？ 讨论如何还添加数据库约束以确保数据完整性。 您将添加哪些索引？ 您将如何推出迁移以防止停机？

Once you get your hardcoded -> dumb -> better solution, talk about how you would refactor it given more time. Would you create a module for this? What about a service object? What about putting some of this logic in a background job? Discuss the tradeoffs.

一旦获得了硬编码->哑巴->更好的解决方案，请讨论在更多时间下如何重构它。 您会为此创建一个模块吗？ 服务对象呢？ 将某些逻辑放在后台工作怎么样？ 讨论权衡。

Now why is this so important?

现在为什么如此重要？

Most interview questions are aimed at the lowest common denominator—meaning the very basic requirements of the job. The challenge or questions themselves are usually not designed to test the top end of someone's skill. The interview is probably not going to pull the information out of you, so you have to supply that information.

大多数面试问题都针对最低的公分母 -这是工作的最基本要求。 挑战或问题本身通常并非旨在考验某人技能的最高水平 。 面试可能不会从您那里获取信息，因此您必须提供该信息。

So while you're talking through your thought process, mention all of the things you would incorporate in a real-life application or codebase and discuss them.

因此，当您讨论自己的思想过程时，请提及将要结合到现实应用程序或代码库中的所有内容并进行讨论。

额外的技巧和窍门抓包 (Extra tips & tricks grab bag)

So that's how you should approach your interview and tackle whatever challenge you're given.

因此，这就是您应该如何进行面试并应对遇到的任何挑战的方法。

Here's a few extra tricks that can sometimes be employed for slight advantages.

这里有一些额外的技巧，有时可以利用这些技巧获得一些好处。

技巧1：了解常见问题 (Trick 1: Know the common problems)

There are a few common problems that show up often in interviews (especially on whiteboards). You should be familiar with these problems because they're sort of like questions you know are going to be on the test.

面试中经常会出现一些常见问题(尤其是在白板上)。 您应该熟悉这些问题，因为它们有点像您知道要测试的问题。

Two of the main ones are FizzBuzz and solving the Fibonacci sequence (make sure you know these).

FizzBu​​zz和解决斐波那契数列是两个主要的过程(请确保您知道这些)。

Now a word of warning: you don't ever want to put down a memorized solution in an interview. That can only go poorly (and I've witnessed it happen). You do however want to be familiar with the solution—and be able to recreate it from scratch.

现在要提个警告：您永远都不想在面试中写下记忆深刻的解决方案。 那只会变得很糟(我目睹了这种情况的发生)。 但是，您确实希望熟悉该解决方案，并能够从头开始重新创建它。

So use your interview question prep books, yes, but make sure you understand the solution, can explain it, and can re-create it from scratch. A memorized answer isn't going to get you anywhere here.

因此，可以使用面试题准备书，但是请确保您了解解决方案，可以解释它并可以从头开始重新创建它。 一个记住的答案不会带你到这里。

技巧2：通常可以查看文档 (Trick 2: It's usually ok to look at the docs)

In all of the interviews I've been in or a part of, no one has cared if you look up the standard library or package docs. Interviewers are not ok with you looking up the answer (so I would avoid StackOverflow), but consulting the references is usually fair game. When in doubt, see Tip #1 and ask for clarification.

在我去过或参与过的所有采访中，如果您查找标准库或打包文档，都不会有人在意。 面试官不满意您查找答案 (因此我会避免使用StackOverflow)，但是查阅参考文献通常是公平的游戏。 如有疑问，请参见技巧1并要求进行澄清。

技巧3：注意视觉提示 (Trick 3: Watch for visual cues)

This is probably my favorite tip/trick. It's not the most useful, but it is kind of fun. One of my interviews I did remotely, and we were using a screen-sharing program and I could see the interviewer's face in the top-right of my screen.

这可能是我最喜欢的提示/技巧。 它不是最有用，但是很有趣。 我的采访之一是远程进行的，当时我们正在使用屏幕共享程序，在屏幕的右上方可以看到访问者的脸。

I noticed out of the corner of my eye as I was coding that the interviewer was nodding their head. Ah ha! A little visual cue to know that I was on the right track.

当我在编码时，我忽然注意到面试官在点头。 啊哈！ 有点视觉上的提示，知道我在正确的轨道上。

Again it's not much, but it could be useful. :)

同样，它虽然不多，但可能很有用。 :)

绝招4：如果是远程的话，请做好设置 (Trick 4: If remote, have a good setup)

Speaking of being remote, if you are remote try to have the best setup you can. This means camera on (if possible setup where you're looking straight into it), good internet, computer plugged into power, a quiet room, glass of water nearby, etc.

说到远程，如果您是远程的，请尝试获得最佳设置。 这意味着需要打开相机(如果可能的话，请设置成直视的位置)，良好的互联网连接，接通电源的计算机，安静的房间，附近的水杯等。

These things shouldn't affect your interview result, but there's no need to annoy the interviewer or give yourself extra stress from internet or noise issues.

这些事情不应该影响您的面试结果，但是没有必要让面试官烦恼或让自己承受来自互联网或噪音问题的额外压力。

技巧5：要风度翩翩！ (Trick 5: Be personable!)

My last trick for you is to be personable.

对你来说，我的最后一招是要风度翩翩。

In your interview, be someone that you would want to work with. Show them your best self.

在面试中，成为您想与之共事的人。 向他们展示你最好的自我。

Interviews can be intimidating, and developers are generally a quieter and more reserved people, but you need to show the people you interact with, "Hey, I'm a fun and nice person to work with."

面试可能令人生畏，开发人员通常是一个安静且更内向的人，但是您需要向与之互动的人展示“嘿，我是一个有趣而友好的人”。

I'm not asking you to be someone you're not. But you don't want to be, according to one of my close friends who interviews people all the time, a "sea creature."

我不是要你成为不是你的人。 但是，根据我一直与人面试的一位亲密朋友所说，您不想成为“海洋生物”。

奖励技巧6：进行所有其他面试准备(如果需要) (Bonus Trick 6: Do all of the other interview prep (if you want))

If you're feeling under-prepared, or this is your first tech interview, do some prep work until you feel comfortable.

如果您准备不足，或者这是您第一次接受技术面试，请做一些准备工作，直到您感到舒适为止。

Read books like Cracking the Coding Interview or practice algorithms and puzzles on HackerRank.

阅读诸如《 破解编码面试》之类的书，或在HackerRank上练习算法和难题。

Read the other great posts on Developer News about interviewing.

阅读《 开发人员新闻》中有关面试的其他精彩文章。

If you're interviewing for a full-stack role, be prepared to setup a new project or test file with test suite from scratch.

如果您要面试全职职位，请准备从头开始使用测试套件设置新项目或测试文件。

Research the company, be ready with great questions about the company or the day-to-day work, etc., etc.

研究公司，对公司或日常工作等方面的重大问题做好准备。

最后：这只是一次采访。 (In the end: it's just an interview.)

In the end, it is what it is.

最后，它就是它。

You'll perform how you perform.

您将执行自己的表演。

You'll be interviewed by the person you'll be interviewed by.

您将由您面试的人面试。

Their interview process will be their interview process.

他们的面试过程将是他们的面试过程。

Maybe you had an off day—maybe the interviewer had an off day.

也许您有一天休息-也许面试官有一天休息。

Afterwards if you feel embarrassed, defeated, or anything else—take a deep breath and let it go! Don't let your Lizard Brain weigh you down. A bad interview is not the end of the world. Your career isn't ruined, your reputation isn't ruined, and your life isn't ruined.

然后，如果您感到尴尬，被打败或其他任何事情，请深呼吸并放手！ 不要让您的蜥蜴脑使您失望。 不好的采访并不是世界末日。 您的职业生涯没有被破坏，您的声誉没有被破坏，您的生活也没有被破坏。

It's just an interview. Learn from it, adapt, and be better the next time.

这只是一次采访。 从中学习，适应并在下一次变得更好。

紧张是可以的 (It's ok to be nervous)

Most people (myself included) get nervous before things like interviews, talks, or presentations.

大多数人(包括我自己)在面试，演讲或演讲之前都会感到紧张。

I used to think of nervousness as a bad thing—a thing I didn't want. And no matter how many times I told myself "don't be nervous"—guess what: it just made me more nervous!

我曾经认为紧张是一件坏事，这是我不想要的事情。 而且无论我告诉自己多少次“别紧张”，都可以猜到：这让我更加紧张！

I've learned to re-think how I view nerves. Nervousness is my body preparing for a fight—that primal fight or flight response.

我学会了重新思考我如何看待神经。 紧张是我准备战斗的身体-原始战斗或逃避React。

But like we said before: this is just an interview. There's no tiger sneaking up on me in the interview room. This primal response isn't necessary.

就像我们之前说的：这只是一次采访。 在采访室里没有老虎偷偷溜走。 此原始响应不是必需的。

I've started retraining myself to view nervousness as a good thing. It means my body and sense are heightening so I can deliver the best performance I can muster.

我已经开始重新训练自己，将紧张感视为一件好事。 这意味着我的身体和感觉正在增强，因此我可以提供自己可以召集的最佳表现。

So, embrace the nerves. They're just prepping you to perform your best.

因此，拥抱神经。 他们只是在准备让您表现最好。

面试是一种技巧 (Interviewing is a skill)

In the end, interviewing is a skill. It takes some studying and a lot of practice to master.

最后，面试是一种技巧。 它需要一些学习和大量实践才能掌握。

So don't beat yourself up if you don't perform how you would have hoped. Keep learning, and keep practicing—you'll get there!

因此，如果您没有按照自己的期望去做，就不要殴打自己。 不断学习，不断练习-您会到达那里！

If you have any questions or comments, feel free to reach out to me on Twitter, and if you want more information on how to prepare for a development career, I write stuff like this on my blog.

如果您有任何疑问或意见，请随时在Twitter上与我联系 ，如果您想了解有关如何为发展事业做准备的更多信息，我会在博客上写类似的内容。

Thanks for reading!

谢谢阅读！

John

约翰

翻译自: https://www.freecodecamp.org/news/interviewing-prep-tips-and-tricks/

mcu比较器技巧和诀窍