高能解析得时候忽略某个字段

by Tanner Christensen

由Tanner Christensen

我们什么时候应该忽略批评? (When Should We Ignore Criticism?)

A fairly well-known and respected graphic designer once openly criticized something I had written and shared publicly. He did a poor job with his feedback however, as his only remark—in its entirety—was: “This guy doesn’t get it.”

一位相当知名和受人尊敬的图形设计师曾经公开批评我写的东西并公开分享。 但是,他的反馈意见做得很差,因为他的全部评论是: “这个家伙不明白。”

The feedback stung, but it also made me question the designer’s intention and understanding of what he was criticizing.

反馈st不休,但这也让我质疑设计师的意图和对他批评的理解。

“This guy doesn’t get it.” What was the “it” he was referring to exactly? How might I begin learning how to “get” whatever “it” was? What could I do to improve and become as seemingly aware and insightful as the critic? He failed to provide any answers. His criticism was hurtful and loud, but ultimately useless.

“这个家伙不明白。” 他确切指的是“它”是什么? 我将如何开始学习如何“获得”任何“东西”? 我可以做些什么来改善和变得像批评家一样看似有知觉? 他没有提供任何答案。 他的批评是痛苦而响亮的,但最终毫无用处。

Of course criticism is important: it can expose us to perspectives we weren’t aware of, uncover flaws in our work, and help us identify areas for learning and growing. Criticism can be generative and help us create a more complete picture of whatever it is we’re trying to do. But some criticism, while obnoxiously loud, will lack any real substance.

当然,批评很重要:它可以使我们了解我们所不了解的观点,发现工作中的缺陷,并帮助我们确定学习和发展的领域。 批评可能会产生影响,并帮助我们更完整地了解我们正在尝试做的事情。 但是有些批评虽然令人讨厌,但缺乏任何实质内容。

Knowing when to tune-in and probe or when to ignore criticism is valuable. It will save you time, help you avoid headaches and heartaches, and get you to a place where you’re growing and producing good work rather than obsessing over the impossible pursuit of perfection.

知道何时调优和探索或何时忽略批评很有价值。 这将节省您的时间,帮助您避免头痛和心痛,并使您到达一个正在成长并产生良好工作的地方,而不是痴迷于对完美的不可能的追求。

In his book Antifragile Nassim Nicholas Taleb writes:

纳西姆·尼古拉斯·塔勒布(Nassim Nicholas Taleb)在《 抗脆弱》一书中写道:

“When you take risks, insults by small men, those who don’t risk anything, are similar to barks by nonhuman animals; you can’t feel insulted by a dog.”

“当你冒险时,小男人的侮辱,那些不冒险的人,就像非人类动物的树皮一样; 你不会被狗侮辱。”

In my example story, this once noble designer may have had some great years of experience, but if the only guidance he can muster to a fellow designer is: “you don’t get it,” he’s wasting his time. He wasn’t helping me, or any of his dutiful followers, just barking like an obnoxious dog.

在我的示例故事中,这位曾经高贵的设计师可能有多年的经验,但是如果他能吸引其他设计师的唯一指导是: “您不明白”,那是在浪费时间。 他并没有帮助我,也没有任何忠实的追随者,只是像讨厌的狗一样吠叫。

When you hear or give criticism you must consider whether it’s additive or generative—is it offering anything that can be built on?—or is it neutral or subtractive?

当您听到或提出批评时,必须考虑它是累加性的还是产生性的-它提供了可以建立的任何东西吗?还是中性或消极性?

If I had listened to the criticism—if I had taken the words to heart and believed that I wasn’t “getting it,” if I had done anything because of the criticism—I’d be no better off. Absolutely unchanged. Because I wouldn’t have had the slightest clue as to any reason the criticism might be true. What was the argument to be made against whatever “it” was I wasn’t getting? What was the way forward, toward understanding?

如果我听了批评的话-如果我牢记这些话并相信我没有“得到它”,如果我因为批评而做了任何事情-我的生活不会更好。 绝对不变。 因为无论出于任何原因 ,我都不会有丝毫的头绪,因为批评可能是真的。 针对我没有得到的任何“争论”,有何论点呢? 理解的前进方向是什么?

I would have learned nothing if I had taken the criticism seriously, because that’s exactly what the criticism had to offer me: nothing.

如果我认真对待批评,我将学不到任何东西,因为这正是批评所提供给我的:没有。

Former VP of Design at Twitter, Mike Davidson, recently wrote about unhelpful feedback:

Twitter前设计副总裁Mike Davidson最近写了有关无用反馈的文章 :

“You should treat your critiques as investigations or explorations and not conclusions.”

“您应该将批评视为调查或探索,而不是结论。”

It’s easy to get distracted by the moans of the critical chastiser, drawn to their own conclusions and fully convinced everyone else should agree with them. They’re the ones who speak up the most, even when they have nothing real, founded, or valuable to say. They bark simply because they want to have a voice, they want to be heard.

批判性追逐者的抱怨很容易分散注意力,得出他们自己的结论,并完全相信其他所有人都应该同意他们的观点。 他们是说话最多的人,即使他们没有真实,无根据或有价值的话。 他们之所以吠叫,是因为他们想表达自己的想法,并且想被别人听到。

Here’s the thing: the unhelpful critic usually doesn’t really understand what it is they’re criticizing in the first place.

事情就是这样:无助的批评家通常并不真正了解他们首先批评的是什么。

While many people are initially reserved in their feedback—either recognizing they don’t have an understanding from which to give feedback, or because they’re working through their thoughts—the unhelpful critic immediately leaps at the opportunity to make a sound. They have to make it known they’re there.

尽管许多人最初对反馈意见持保留态度,要么意识到他们没有反馈的理解力,要么是因为他们正在思考,但无助的批评家立即抓住了发声的机会。 他们必须让他们知道他们在那里。

You’re better off ignoring unhelpful critics because you’ll learn a lot more—a lot faster—if you just keep on doing the work.

您最好不要理会那些无用的批评家,因为如果您继续从事这项工作,您将学到更多(更快)的知识。

Rather than paying attention to the unhelpful critic, you’d be better off trudging forward, patiently seeking the advice of more insightful reviewers. It does you no good to give into the sound of distant dogs barking.

与其去注意无助的批评家,不如继续前进,耐心地寻求更有见地的审稿人的建议。 让远处的狗叫声对您不利。

And here’s the thing: unhelpful critics are easy to identify by a singular, prominent, characteristic. What they say is ultimately devoid of any path forward.

事情就是这样: 无助的批评家很容易通过独特,突出的特征来识别。 他们说的话最终没有任何前进的道路。

Their criticism typically dead-ends or leaves you with more questions than answers. Instead of helping pave a potential way forward, they seek to put an end to your thinking or executions. They are not additive, only subtractive. They do not ask questions or seek to understand, they only bark definitive expressions.

他们的批评通常死胡同,或者给您留下的问题多于答案。 他们没有帮助铺平可能的前进之路,而是寻求结束您的思维或处决。 它们不是加性的,只是减性的。 他们不问问题或寻求理解,只是吠叫确定性的表达。

They don’t have a solution or a clear way to improve the work themselves, so they offer none. All bark, no bite.

他们没有解决方案或明确的方法来改善自己的工作,因此他们一无所获。 全部吠叫,不咬人。

Phrases like: “I don’t like that,” or “This is weak,” or “You don’t get it,” are all incredibly useless phrases when it comes to feedback. What such statements attempt to provoke they miss by not providing any substantial evidence for or—and most importantly—ideas on how to improve the very thing they find themselves critiquing.

诸如“我不喜欢”“这很薄弱”“您不明白”这样的短语在反馈中都是无用的短语。 这些陈述试图通过不提供任何实质性证据或(最重要的是)如何改善他们发现自己正在遭受批评的事情的想法而引起他们错过的东西。

This type of feedback signals a shut down; the critic doesn’t want to engage and the receiver is less likely to want to either. “This is wrong, so don’t bother.” A much better approach is through asking questions, probing to develop empathy and understanding, grounding the conversation or feedback in a common language.

这种类型的反馈表示关闭。 评论家不想参与,接收者也不太可能愿意参与。 “这是错误的,所以不要打扰。” 更好的方法是通过提问,探索同理心和理解力,以通用语言为基础的对话或反馈。

You should take this all to heart, not merely as a way of knowing who to pay attention to when getting critiqued, but also as a measurement of your own ability to give quality feedback.

您应该牢记这一切,不仅是一种了解被批评时应该关注的人的方式,而且还应该作为衡量自己提供质量反馈的能力的一种方式。

If all you have to offer is a singular statement, devoid of any path forward, odds are you don’t really understand what it is you’re trying to say.

如果您所提供的只是一个单一的陈述,而没有任何前进的方向,那么您很可能根本不了解您要说的是什么。

Again a quote from Mike Davidson:

再次引用Mike Davidson的话:

“A good rule of thumb is: if a problem seems simple to you, you probably don’t fully understand it. You certainly might, but you probably don’t.”

“一个好的经验法则是:如果问题对您而言很简单,那么您可能就不完全理解它。 您当然可以,但您可能不会。”

翻译自: https://www.freecodecamp.org/news/when-should-we-ignore-criticism-764bef3ff2e4/

高能解析得时候忽略某个字段

高能解析得时候忽略某个字段_我们什么时候应该忽略批评?相关推荐

  1. java 对象复制字段_利用Java反射机制实现对象相同字段的复制

    一.如何实现不同类型对象之间的复制问题? 1.为什么会有这个问题? 近来在进行一个项目开发的时候,为了隐藏后端数据库表结构.同时也为了配合给前端一个更友好的API接口文档(swagger API文档) ...

  2. 返回json格式 不忽略null字段

    返回json格式 不忽略null字段 发布于 353天前  作者 king666  271 次浏览  复制  上一个帖子  下一个帖子  标签: json 如题,一个实体的某个字段如果为null,在转 ...

  3. mybatis-plus忽略映射字段

    mybatis-plus使用对象属性进行SQL操作,经常会出现对象属性非表字段的情况,忽略映射字段使用以下注解: @TableField(exist = false):表示该属性不为数据库表字段,但又 ...

  4. gitignore忽略文件夹_原创 | 详解gitignore的使用方法,让你尽情使用git add .

    点击上方蓝字,关注并星标,和我一起学技术. 大家好,欢迎来到周一git专题. 今天和大家聊聊gitignore的作用,其实如果你英文还可以的话,你应该已经基本上猜到它的作用了.ignore在英文当中的 ...

  5. git 命令行忽略提交_Git忽略提交的3种方法及Git忽略规则

    在使用Git的过程中,我们喜欢有的文件比如日志,临时文件,编译的中间文件等不要提交到代码仓库,这时就要设置相应的忽略规则,来忽略这些文件的提交. Git 忽略文件提交的方法 有三种方法可以实现忽略Gi ...

  6. 迈克尔 杰克逊mv_杰克逊JSON解析错误– UnrecognizedPropertyException:无法识别的字段,未标记为可忽略[已解决]...

    迈克尔 杰克逊mv 在解析从我们的一个RESTful Web服务接收到的JSON字符串时,我收到此错误"线程" main"中的异常com.fasterxml.jackso ...

  7. 杰克逊JSON解析错误-UnrecognizedPropertyException:无法识别的字段,未标记为可忽略[已解决]...

    在解析从我们的一个RESTful Web服务接收到的JSON字符串时,我收到此错误"线程" main"中的异常com.fasterxml.jackson.databind ...

  8. java如何忽略过程值_如果值为null,如何告诉Jackson在序列化期间忽略某个字段?...

    回答(16) 2 years ago mapper.setSerializationInclusion(Include.NON_NULL); 要么: @JsonInclude(Include.NON_ ...

  9. sql输出带颜色的字段_带你走进MySQL数据库(MySQL入门详细总结一)

    导读:关于MySQL用三篇文章带你进入MySQL的世界. 文章目录 1.MySQL 2.MySQL的使用 3.MySQL概述 4.导入数据 5.sql语句 1.查询 2.排序(升序,降序) 3.分组函 ...

最新文章

  1. 模糊测试工具Simple Fuzzer
  2. rsynv+inotify触发试实时同步
  3. Angular如何判断某个DOM节点包含Directive
  4. Go语言-基本的http请求操作
  5. setpriority_Java Thread类的最终void setPriority(int priority)方法(带示例)
  6. 行为型模式——状态模式(十一)
  7. 常用连续型分布介绍及R语言实现
  8. glog学习(二):glog主要接口和类分析
  9. linux系统下Gaussian16和Gaussian view6的详细安装步骤
  10. 光纤光缆那些纤常识【华光昱能光知识】
  11. java软件工程师工作业绩_java软件工程师的工作描述怎么写
  12. 爱奇艺多模态短视频内容标签技术及应用
  13. 显卡驱动设备状态代码31
  14. “分类” 与 “回归”的概念及区别详解
  15. Android maven-publish使用
  16. Java| MANIFEST.MF讲解
  17. How to set dev_loss_tmo and fast_io_fail_tmo persistently, using a udev rule
  18. 【芯片应用】DAC8554
  19. 数据分析从0到1之AARRR模型 - Blog2
  20. 邵阳一中2021高考成绩查询,2021年邵阳高考最高分多少分,历年邵阳高考状元

热门文章

  1. 常见运行时异常 java 114982568
  2. 案例 银行取款 java 1615136927
  3. 枚举类型 c# 1201
  4. bootstrap-按钮的创建
  5. mysqld: [Warning] World-writable config file ‘/etc/my.cnf‘ is ignored.问题解决
  6. html常用标签6-表单标签
  7. Linux驱动技术(六) _内核中断
  8. Android Studio 代码混淆
  9. 网络基础---IP编址
  10. AIX下密码永不过期