同情机器人_同情心如何帮助您建立更好的工作文化

同情机器人

Empathy is one of those things that can help in any part of life whether it’s your family, friends, that special person and even also at work. Understanding what empathy is and how it effects people took me long time. I struggle with human interactions and I am not ashamed to admit it, so I wanted to share my experience, as to what I have found from all of it.

同情是可以帮助生活中任何部分的事物之一，无论是您的家人，朋友，那个特殊的人， 甚至在工作中。 了解同情是什么以及它如何影响人们，我花了很长时间。我在与人之间的互动中挣扎，我不为自己的接受而感到羞耻，所以我想分享我的经验，以及从所有事物中发现的东西。

I am full stack javascript developer. I love code. Javascript is my favorite language and for as long as I can remember I have considered my self as a one-man-army. I get the part where you have to say this in your interviews: “I am a team player & a people person”, and I have said that. But the truth is I am not and rather I am learning as I go.

我是全栈javascript开发人员。我喜欢代码。 Javascript是我最喜欢的语言，并且只要我记得我就一直将自己视为一个单兵。在采访中， 我要说的是 ： “我是一个团队合作者和一个人”，我就是这么说的。但是事实是我不是，而是我正在学习。

The biggest thing I have realized is throughout your experience, what will matter is the lives you have impacted. The relationships you have built. I promise you tech stacks will change and you’ll grow old eventually. Programming might not be a suitable career choice at some point for whatever reason. What will matter at the end is the relationships you’ve built along the way.

我认识到的最大事情就是您的整个经历，重要的是您受影响的生活。 您建立的关系。 我保证您的技术堆栈会发生变化，并且最终会变老。出于某种原因，在某些时候编程可能不是一个合适的职业选择。最后重要的是您在此过程中建立的关系。

什么是同理心？ (What is empathy?)

Empathy is the ability to understand and share the feelings of another. It is the act of putting yourself in others’ shoes and seeing a problem from their point of view.

同理心是理解和分享他人感受的能力。这是使自己陷入困境并从他人的角度看问题的行为。

In my day work, I get to be a team lead and I get to be responsible for some really genuine and brilliant people. All of them are diverse and bring something unique to the table. Some are fresh in the industry others are experienced. The only way I can develop a really good and productive team who are in sync with each other and at the best of their abilities, is if I can understand their issues from their POV. Whether it is with code or something else.

在我的日常工作中，我要成为团队负责人，并对一些真正真诚和才华横溢的人负责。它们都各不相同，并为餐桌带来了独特之处。有些是行业内新鲜的，有些是经验丰富的。我可以建立一个真正优秀和富有生产力的团队的唯一方法是彼此协作，并尽其所能，这就是我可以从他们的POV中了解他们的问题。无论是代码还是其他东西。

移情会带来什么好处？ (What good will empathy do?)

There are so many benefits of having empathy, so I’ll just state a few. The end result of it is

拥有同理心的好处很多，所以我只列举一些。最终结果是

a happy team
一个快乐的团队
a well groomed end-product
精心修饰的最终产品
good work culture.
良好的工作文化。

So, like many other problems we face as software engineers, we tend to solve problems by devising an algorithm. Here is “pseudo code” for empathy.

因此，就像我们作为软件工程师面临的许多其他问题一样，我们倾向于通过设计算法来解决问题。这是移情的“伪代码”。

1- better understanding of your colleagues: If you understand them better., you can help them better.

1-更好地了解您的同事：如果您更好地了解他们，则可以更好地帮助他们。

2- The unsaid things: Your team might not share everything with you. Based on their body-language, tone, voice, you will have a better idea of their situation.

2-未说的事情：您的团队可能不会与您共享所有内容。根据他们的肢体语言，语气，声音，您会更好地了解他们的处境。

3- Resolving conflicts: When you understand the unsaid things, you can address them and make your team members feel heard. This is the first step of resolving a conflict.

3-解决冲突：当您了解未说的内容时，您可以解决这些问题并使您的团队成员感到被听到。这是解决冲突的第一步。

I have always said this: the first point of solving any problem is knowing what the problem is.
我一直这样说：解决任何问题的第一步就是知道问题是什么。

4- Getting empathy back from your team: There are times when you have to be straight with the team. Maybe your team is slacking, not working effectively or maybe a deadline is closing in and you have to ask them to work overtime a bit (there are some days when the client comes first).

4-从团队中获得同情：有时候，您必须与团队保持直率。也许您的团队有些懈怠，工作效率低下，或者截止日期临近，您必须要求他们加班(有些时候客户是第一位的)。

In such cases your team might mistrust your intentions. But if you have some inclination of their understanding behind their motivation and point of view, it becomes a bit simpler to gain their trust and convince them of your point of view.

在这种情况下，您的团队可能会怀疑您的意图。但是，如果您对他们的动机和观点有所了解，那么获得他们的信任并说服他们相信您的观点会变得更加简单。

Before you know it, you will somehow become more in tune with your team’s needs. Not a clairvoyant to be exact, but you will somehow be able to predict your team’s follow up questions and answer them better. You will also be able to understand what is holding them back from their true potential

在不知不觉中，您将以某种方式变得更加适应团队的需求。确切地说，这不是千篇一律，但您将能够以某种方式预测团队的后续问题并更好地回答。您还将能够了解是什么阻碍了他们的真正潜力

工作场所的同理心 (Empathy at the workplace)

It is without any doubt that empathy can help in any kind of job that involves people, and our tech industry is no exception. This is valid even if you work remotely because the messages you see in the chat room are not from bots but from actual people sitting on the other side of the computer.

毫无疑问，同情心可以帮助任何涉及人的工作，我们的科技行业也不例外。即使您是远程工作，这也是有效的，因为您在聊天室中看到的消息不是来自漫游器，而是来自坐在计算机另一侧的实际人员。

One frequent situation where we can forget about empathy is during a code review, which I talk about below.

我们经常会忘记同理心的一种常见情况是在代码审查期间，我在下面讨论。

Another problem is when 2 people from different teams need to work together to solve a problem or work on a feature. This can produce an “us versus them” attitude. This can be the case if the teams are from different domains or if it’s the same team divided working from different geographic locations.

另一个问题是，来自不同团队的2个人需要一起解决问题或处理某个功能。这可能会产生“我们与他们对抗”的态度。如果团队来自不同的领域，或者是来自不同地理位置的同一个团队，那就可能是这种情况。

A variant of “us versus them” can be “developer versus quality assurance” or “developer versus project managers”. What happens is developers end up taking a very defensive stance against managers, and we (developers) don’t try hard enough to understand their side of story (managers/QA). Getting to know the other side would certainly help to empathize with them. If we can somehow understand what they do, why they do it, it will certainly help in building a better relationship.

“我们与他们”的变体可以是“开发人员与质量保证”或“开发人员与项目经理”。发生的事情是开发人员最终对管理人员采取了非常防御的态度，而我们(开发人员)没有尽全力去理解他们的故事(经理/质量保证)。认识对方肯定会帮助他们。如果我们能以某种方式了解他们的工作，为什么这样做，那肯定会有助于建立更好的关系。

Daniel Westheide has written an excellent article called “The Empathic Programmer.” Do read it at your pleasure.

丹尼尔·韦斯海德(Daniel Westheide )撰写了一篇出色的文章，名为《同情程序员》。请随便阅读。

让我们从更好的代码审查开始 (Let’s start with better code reviews)

Before we start off with better code reviews, it is so important to make your team realize what a “Prime Directive” is:

在我们开始进行更好的代码审查之前，让您的团队意识到什么是“首要指令”非常重要：

Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.” –Norm Kerth
无论我们发现什么，我们都理解并真正相信，鉴于他们当时所知道的，他们的技能和能力，可用的资源以及当前的状况，每个人都尽了最大的努力。” –Norm Kerth

Once this attitude is established and realized by your team, it does 2 things: First, the person reviewing the code knows that their job is not to judge the person who wrote the code, but rather to make improvements on the code. And second, the person who is getting their code reviewed knows that the feedback they are getting is not a personal attack on them, but an opportunity for growth.

一旦您的团队确立并实现了这种态度，它就会做两件事：首先，检查代码的人知道，他们的工作不是判断代码的编写者，而是对代码进行改进。其次，正在审核其代码的人知道，所获得的反馈不是对他们的人身攻击，而是成长的机会。

I strongly believe the only way of growing is when you get feedback.
我坚信，增长的唯一途径就是获得反馈。

更好地塑造我们的语言 (Better shaping our words)

Words, if chosen carefully, can either make this world a better place to live in or hell. It is not guns and ammo. Words are, I believe, the most dangerous weapon at our disposal. Let’s consider the following comment:

如果谨慎选择话语，可能会使这个世界成为一个更好的生活场所或陷入地狱。不是枪支弹药。我认为，言语是我们可以使用的最危险的武器。让我们考虑以下评论：

This is the wrong way to structure test, it handles way to many use cases altogether
这是结构测试的错误方法，它对许多用例都进行了处理

We could instead say something like this:

我们可以这样说：

I think for better readability we can divide these tests into separate modules. Here is a reference from http://some-dummy-reference/example
我认为，为了提高可读性，我们可以将这些测试分成单独的模块。 这是来自http：// some-dummy-reference / example的参考

Another example of a more negative comment like this would be:

这样的负面评论的另一个例子是：

These 3 lines belong in a separate method.
这3行属于单独的方法。

Instead, we can tweak our words a bit and say:

取而代之的是，我们可以稍微调整一下措词，然后说：

What do you think of extracting these lines into a separate method, to handle calculations separately?
您如何将这些行提取到单独的方法中以分别处理计算结果呢？

This gives the other person some power and makes them feel that their opinions matter and that they have a say in this matter.

这给了对方一些力量，使他们觉得自己的意见很重要，并且对此事有发言权。

可以有意见 (It is okay to have opinions)

People who know me can vouch for the fact that I argue a lot and I strongly believe in this. Being a software engineer, everything should be 0’s & 1’s. Think of yourself in The Matrix with the chosen one (Neo).

认识我的人可以保证我会争论很多，我对此深信不疑。作为软件工程师，一切都应该为0和1。在所选的《黑客帝国》(Neo)中想想自己。

So let’s say there is a conflict about anything, perhaps deciding to go for a design pattern A rather than design pattern B, where I am in favor of the latter option. I need to come up with a reason for why I believe my suggested option will work better with the use case that is presented to us.

因此，假设存在任何冲突，也许是决定采用设计模式A而不是设计模式B，我赞成后者。我需要提出一个理由，说明为什么我认为我建议的选项可以更好地与呈现给我们的用例一起使用。

It is easy to accept and go with the flow, while saying NO is hard because people will argue with you about it. So you need to know why the option you support is better than the one proposed by the team. I honestly love this kind of culture where the team can have a meaningful discussion about choosing design approaches. That is what I believe engineering is all about.

很容易接受并顺其自然，但说“不”很困难，因为人们会与您争论。因此，您需要知道为什么您支持的选项比团队提出的选项更好。老实说，我喜欢这种文化，团队可以就选择设计方法进行有意义的讨论。我认为这就是工程的全部意义。

整理您的论点 (Organizing Your Arguments)

If the code review that you are having is about style, like tabs vs spaces or about extra white space etc, then that means your team isn’t well aware of the style guide being followed in your project. And a PR comment isn’t a valid place to have that argument.

如果您所进行的代码审查与样式有关，例如制表符与空格或多余的空白等，则意味着您的团队不太了解项目中要遵循的样式指南。公关评论不是有该论点的有效地方。

You can maybe integrate some cool linting tools to automate this process, like EsLint. I wrote an article earlier about writing clean code called These tools will help you write clean code — check it out.

您也许可以集成一些很酷的整理工具来自动化该过程，例如EsLint 。我之前写过一篇有关编写干净代码的文章，名为“ 这些工具将帮助您编写干净的代码 -进行检查”。

If, on the other hand, the code review comments are too high level, the commentator does have the right to clarify his opinion. But a better place to have this discussion is on a piece of paper before implementing the code itself. Final code review shouldn’t be an optimal place to discuss how to tackle the problem.

另一方面，如果代码审查注释的等级太高，则注释者确实有权澄清其意见。但是，在实现代码本身之前，最好在纸上进行讨论。最终代码审查不应是讨论如何解决问题的最佳场所。

没照顾 (Failing to care)

Another problem with code reviews is people don’t care about them (I used to be one of them, until someone wrote bad code in my code. Never again.)

代码审查的另一个问题是人们不关心它们(我曾经是其中的一个，直到有人在我的代码中写了不好的代码。再也不来了。 )

I can understand. The code reviews are not the most fun part of the job. But they are the most important part. The part where it becomes really difficult is when you have a very big PR to approve — and I have put my team in that position more times then I can count. But it has been for important reasons. An ideal situation is to keep your PR as small as possible so the code review is easy and not hard on the eyes.

我能够了解。代码审查不是工作中最有趣的部分。但是它们是最重要的部分。真正困难的部分是当您需要批准大量公关时，而我让我的团队在该职位上的任职次数超过了我可以数的时间。但这是有重要原因的。理想的情况是使PR尽可能小，这样代码审查就容易而又不费劲。

If a big code review needs to happen, you can let your team know before hand and do it altogether as a fun exercise. Think of it as a team building activity.

如果需要进行大型代码审查，则可以先让您的团队知道，然后进行一次有趣的练习。将其视为团队建设活动。

To make this problem a bit more approachable, maybe you can present the code reviews in a better way:

为了使此问题更容易解决，也许您可以采用更好的方式呈现代码审查：

attach screenshots of before and after the PR
附加PR之前和之后的屏幕截图
explain what the PR does and give context on the background
解释PR的作用并提供背景信息
give references on your approach
提供有关您的方法的参考
be ready for feedback — what doesn’t break you only makes you stronger
准备好接受反馈-不会破坏您的东西只会使您变得更坚强

April Wensel has a brilliant article on this called “3 Code Review Pitfalls and How to Avoid Them”.

April Wensel在这方面有一篇出色的文章，名为“ 3 Code Review陷阱和如何避免它们 ”。

So let’s promise be kind, be humble, and be the hardest working person in the room.

因此，让我们保证要仁慈，谦虚并成为会议室中最努力的人。

结语 (Wrapping up)

No one is born with talent, it is all hard work. The reason someone is where they are is because they had the guts and the persistence day in and day out. If you want to be good at something you need to practice it. Empathy is like that as well. You need to practice it everyday to be good at it. Simple as that.

没有人是天生的，这是所有的努力。某人之所以在这里的原因是因为他们日复一日地拥有勇气和毅力。如果您想擅长某事，则需要练习。同理心也是如此。您需要每天练习以精通它。就那么简单。

So let’s sum it up;

因此，让我们总结一下；

Put yourself in your team members’ shoes, and try to understand things from their point of view.
把自己放在团队成员的鞋上，并尝试从他们的角度理解事物。
Be active in asking questions. If you see your team member down, just ask them about the issue. Asking them shows that you are invested in their well being and happiness.
积极提问。如果您看到您的团队成员感到沮丧，只需向他们询问该问题。向他们询问表明您对他们的幸福和幸福有所投入。
Stop judging people. Everyone is here to work to make a good living and support themselves and their loved ones. If you get a feedback from someone, think of it as a constructive criticism and improve yourself.
停止评判人。每个人都在这里工作，以过上幸福的生活，并养活自己和亲人。如果您收到某人的反馈，请将其视为建设性的批评并改善自己。
Share the load if your team is overwhelmed. Jump in help them out. Give them an extra hand. If it is in your hands, maybe give them a day off so they can rest. This way they know that you as a team lead appreciate them for your hard work.
如果您的团队不堪重负，请分担负担。跳进来帮助他们。给他们更多的帮助。如果在您的手中，请给他们休息一天，以便他们休息。这样，他们知道您作为团队的领导者会感谢他们的辛勤工作。
Try to learn about how to be empathetic in your free time. Personally, books have helped me a lot and there is such good content on the internet if you want to read up.
尝试了解如何在空闲时间变得富有同情心。就个人而言，书籍对我有很大帮助，如果您想阅读，互联网上有如此好的内容。
Be attentive and a keen listener. You don’t always have to speak. Sometimes just being there and listening helps.
细心和敏锐的听众。您不必总是讲话。有时候，只是在那里，聆听会有所帮助。
And most of all, GIVE RESPECT! To everyone — your seniors and juniors, everyone! That includes the janitor in the same building as the CEO. Every human being deserves respect.
最重要的是，给予尊重！对于每个人-您的老年人和大三学生，大家！其中包括与首席执行官在同一建筑物中的看门人。每个人都应该得到尊重。