document/TranslateProject
2
0
Fork 0
mirror of https://github.com/LCTT/TranslateProject.git synced 2024-12-23 21:20:42 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #21176 from Chao-zhi/translate-MjAyMTAyMTYgV2hhdCBkb2VzIGJlaW5nIC10ZWNobmljYWwtIG1lYW4ubWQK

Browse Source 
translate done: 20210216 What does being -technical- mean.md
This commit is contained in:
Xingyu.Wang 2021-02-28 10:46:47 +08:00 committed by GitHub
commit d0adc044a4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 168 additions and 177 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

177
sources/talk/20210216 What does being -technical- mean.md
View File

@ -1,177 +0,0 @@
[#]: collector: (lujun9972)
[#]: translator: (Chao-zhi)
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (What does being 'technical' mean?)
[#]: via: (https://opensource.com/article/21/2/what-technical)
[#]: author: (Dawn Parzych https://opensource.com/users/dawnparzych)
What does being 'technical' mean?
======
Dividing people into "technical" and "non-technical" labels harms people
and organizations. Learn why in part 1 of this series.
![question mark in chalk][1]
The word "technical" describes many subjects and disciplines: _technical_ knock-out, _technical_ foul, _technical_ courses for rock-climbing competitions, and _technical_ scores for figure skating in sports. The popular cooking show _The Great British Bake-Off_ includes a _technical_ baking challenge. Anybody who has participated in the theatre may be familiar with _technical_ week, the week before the opening night of play or musical.
As you can see, the word _technical_ does not apply strictly to software engineering and operations, so when we call a person or a role "technical," what do we mean, and why do we use the term?
Over my 20-year career in tech, these questions have intrigued me, so I decided to explore this through a series of interviews. I am not an engineer, and I don't write code, yet this does not make me non-technical. But I'm regularly labeled such. I consider myself technical, and through this series, I hope you will come to understand why.
I know I'm not alone in this. It is important to discuss because how a person or role is defined and viewed affects their confidence and ability to do their job well. If they feel crushed or disrespected, it will bring down their work quality and squash innovation and new ideas. It all trickles down, you see, so how can we improve this situation?
I started by interviewing seven people across a variety of roles.
In this series, I'll explore the meaning behind the word "technical," the technical continuum, the unintended side effects of categorizing people as technical or non-technical, and technical roles that are often considered non-technical.
### Defining technical and non-technical
To start, we need definitions. According to Dictionary.com, "technical" is an adjective with multiple meanings, including:
* Belonging or pertaining to an art, science, or the like
* Skilled in or familiar in a practical way with a particular art or trade
* Technically demanding or difficult (typically used in sports or arts)
The term "non-technical" is often used in tech companies to describe people in non-engineering roles. The definition of "non-technical" is "not relating to, characteristic of, or skilled in a particular field of activity and its terminology."
As somebody who writes and speaks about technology, I consider myself technical. It is impossible to write or speak about a technical subject if you aren't familiar with the field and the terminology. With this understanding, everyone who works in tech is technical.
### Why we assign labels
So why does technical vs. non-technical matter in the technology field? What are we trying to achieve by assigning these labels? Is there a good reason, was there a good reason, and have we gotten away from those reasons and need to re-evaluate? Let's discuss.
When I hear people talk about technical vs. non-technical people, I can't help but think of the Dr. Seuss story [_The Sneetches_][2]. Having a star (or not) was seen as something to aspire to. The Sneetches got into an infinite loop trying to achieve the right status.
Labels can serve a purpose, but when they force a hierarchy of one group being viewed as better than another, they can become dangerous. Think about your organization or your department: Which group—sales, support, marketing, QA, engineering, etc.—is above or below another in importance?
Even if it's not spoken directly or written somewhere, there is likely an understood hierarchy. These hierarchies often exist within disciplines, as well. Liz Harris, a technical content manager, says there are degrees of "technicalness" within the technical writing community. "Within technical writers, there's a hierarchy where the more technical you are, the more you get paid, and often the more you get listened to in the technical writing community."
The term "technical" is often used to refer to the level of depth or expertise a person has on a subject. A salesperson may ask for a technical resource to help a customer. By working in tech, they are technical, but they need somebody with deeper expertise and knowledge about a subject than they have. So requesting a technical resource may be vague. Do you need a person with in-depth knowledge of the product? Do you need a person with knowledge of the infrastructure stack? Or somebody to write down steps on how to configure the API?
Instead of viewing people as either technical or not, we need to start viewing technical ability as a continuum. What does this mean? Mary Thengvall, a director of developer relations, describes how she categorizes the varying depths of technical knowledge needed for a particular role. For instance, projects can require a developer, someone with a developer background, or someone tech-savvy. It's the people who fall into the tech-savvy category who often get labeled as non-technical.
According to Mary, you're tech-savvy if "you can explain [a technical] topic, you know your way around the product, you know the basics of what to say and what not to say. You don't have to have a technical background, but you need to know the high-level technical information and then also who to point people to for more information."
### The problem with labels
When we're using labels to get specific about what we need to get a job done, they can be helpful, like "developer," "developer background," and "tech-savvy." But when we use labels too broadly, putting people into one of two groups can lead to a sense of "less than" and "better than."
When a label becomes a reality, whether intended or not, we must look at ourselves and reassess our words, labels, and intentions.
Senior product manager Leon Stigter offers his perspective: "As a collective industry, we are building more technology to make it easier for everyone to participate. If we say to everyone, 'you're not technical, or 'you are technical' and divide them into groups, people that are labeled as non-technical may never think, 'I can do this myself.' We actually need all those people to really think about where we are going as an industry, as a community, and I would almost say as human beings."
#### Identity
If we attach our identities to a label, what happens when we think that label no longer applies? When Adam Gordon Bell moved from being a developer to a manager, he struggled because he always identified as technical, and as a manager, those technical skills weren't being used. He felt he was no longer contributing value. Writing code does not provide more value than helping team members grow their careers or making sure a project is delivered on time. There is value in all roles because they are all needed to ensure the creation, execution, and delivery of goods and services.
"I think that the reason I became a manager was that we had a very smart team and a lot of really skilled people on it, and we weren't always getting the most amazing work done. So the technical skills were not the limiting factor, right? And I think that often they're not," says Adam.
Leon Stigter says that the ability to get people to work together and get amazing work done is a highly valued skill and should not be less valued than a technical role.
#### Confidence
[Impostor syndrome][3] is the inability to recognize your competence and knowledge, leading to reduced confidence and the ability to get your work done and done well. Impostor syndrome can kick in when you apply to speak at a conference, submit an article to a tech publication, or apply for a job. Impostor syndrome is the tiny voice that says:
* "I'm not technical enough for this role."
* "I know more technical people that would do a better job delivering this talk."
* "I can't write for a technical publication like Opensource.com. I work in marketing."
These voices can get louder the more often you label somebody or yourself as non-technical. This can easily result in not hearing new voices at conferences or losing talented people on your team.
#### Stereotypes
What image do you see when you think of somebody as technical? What are they wearing? What other characteristics do they have? Are they outgoing and talkative, or are they shy and quiet?
Shailvi Wakhlu, a senior director of data, started her career as a software engineer and transitioned to data and analytics. "When I was working as a software engineer, a lot of people made assumptions about me not being very technical because I was very talkative, and apparently that automatically means you're not technical. They're like, 'Wait. You're not isolating in a corner. That means you're not technical,'" she reports.
Our stereotypes of who is technical vs. non-technical can influence hiring decisions or whether our community is inclusive. You may also offend somebody—even a person you need help from. Years ago, I was working at the booth at a conference and asked somebody if I could help them. "I'm looking for the most technical person here," he responded. He then went off in search of an answer to his question. A few minutes later, the sales rep in the booth walked over to me with the gentleman and said, "Dawn, you're the best person to answer this man's question."
#### Stigma
Over time, we've inflated the importance of "technical" skills, which has led to the label "non-technical" being used in a derogatory way. As technology boomed, the value placed on people who code increased because that skill brought new products and ways of doing business to market and directly helped the bottom line. However, now we see people intentionally place technical roles above non-technical roles in ways that hinder their companies' growth and success.
Interpersonal skills are often referred to as non-technical skills. Yet, there are highly technical aspects to them, like providing step-by-step instructions on how to complete a task or determining the most appropriate words to convey a message or a point. These skills also are often more important in determining your ability to be successful at work.
**[Read next: [Goodbye soft skills, hello core skills: Why IT must rebrand this critical competency][4]]**
Reading through articles and definitions on Urban Dictionary, it's no wonder people feel justified in their labeling and others develop impostor syndrome or feel like they've lost their identity. When performing a search online, Urban Dictionary definitions often appear in the top search results. The website started about 20 years ago as a crowdsourced dictionary defining slang, cultural expressions, and other terms, and it has turned into a site filled with hostile and negative definitions.
Here are a few examples: Urban Dictionary defines a non-technical manager as "a person that does not know what the people they manage are meant to do."
Articles that provide tips for how to talk to "non-technical" people include phrases like:
* "If I struggled, how on earth did the non-technical people cope?"
* "Among today's career professionals, developers and engineers have some of the most impressive skill sets around, honed by years of tech training and real-world experience."
These sentences imply that non-engineers are inferior, that their years of training and real-world experiences are somehow not as impressive. One person I spoke to for this project was Therese Eberhard. Her job is what many consider non-technical. She's a scenic painter. She paints props and scenery for film and theatre. Her job is to make sure props like Gandalf's cane appear lifelike rather than like a plastic toy. There's a lot of problem-solving and experimenting with chemical reactions required to be successful in this role. Therese honed these skills over years of real-world experience, and, to me, that's quite impressive.
#### Gatekeeping
Using labels erects barriers and can lead to gatekeeping to decide who can be let into our organization, our teams, our communities.
According to Eddie Jaoude, an open source developer, "The titles 'technical,' 'developer,' or 'tester' create barriers or authority where it shouldn't be. And I've really come to the point of view where it's about adding value to the team or for the project—the title is irrelevant."
If we view each person as a team member who should contribute value in one way or another, not on whether they write documentation or test cases or code, we will be placing importance based on what really matters and creating a team that gets amazing work done. If a test engineer wants to learn to write code or a coder wants to learn how to talk to people at events, why put up barriers to prevent that growth? Embrace team members' eagerness to learn and change and evolve in any direction that serves the team and the company's mission.
If somebody is failing in a role, instead of writing them off as "not technical enough," examine what the problem really is. Did you need somebody skilled at JavaScript, and the person is an expert in a different programming language? It's not that they're not technical. There is a mismatch in skills and knowledge. You need the right people doing the right role. If you force somebody skilled at business analysis and writing acceptance criteria into a position where they have to write automated test cases, they'll fail.
### How to retire the labels
If you're ready to shift the way you think about the labels technical and non-technical, here are a few tips to get started.
#### Find alternative words
I asked everyone I interviewed what words we could use instead of technical and non-technical. No one had an answer! I think the challenge here is that we can't boil it down to a single word. To replace the terms, you need to use more words. As I wrote earlier, what we need to do is get more specific.
How many times have you said or heard a phrase like:
* "I'm looking for a technical resource for this project."
* "That candidate isn't technical enough."
* "Our software is designed for non-technical users."
These uses of the words technical and non-technical are vague and don't convey their full meaning. A truer and more detailed look at what you need may result in:
* "I'm looking for a person with in-depth knowledge of how to configure Kubernetes."
* "That candidate didn't have deep enough knowledge of Go."
* "Our software is designed for sales and marketing teams."
#### Embrace a growth mindset
Knowledge and skills are not innate. They are developed over hours or years of practice and experience. Thinking, "I'm just not technical enough" or "I can't learn how to do marketing" reflects a fixed mindset. You can learn technical abilities in any direction you want to grow. Make a list of your skills—ones you think of as technical and some as non-technical—but make them specific (like in the list above).
#### Recognize everyone's contributions
If you work in the tech industry, you're technical. Everyone has a part to play in a project's or company's success. Share the accolades with everyone who contributes, not only a select few. Recognize the product manager who suggested a new feature, not only the engineers who built it. Recognize the writer whose article went viral and generated new leads for your company. Recognize the data analyst who found new patterns in the data.
### Next steps
In the next article in this series, I'll explore non-engineering roles in tech that are often labeled "non-technical."
--------------------------------------------------------------------------------
via: https://opensource.com/article/21/2/what-technical
作者：[Dawn Parzych][a]
选题：[lujun9972][b]
译者：[Chao-zhi](https://github.com/Chao-zhi)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/dawnparzych
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/question-mark_chalkboard.jpg?itok=DaG4tje9 (question mark in chalk)
[2]: https://en.wikipedia.org/wiki/The_Sneetches_and_Other_Stories
[3]: https://opensource.com/business/15/9/tips-avoiding-impostor-syndrome
[4]: https://enterprisersproject.com/article/2019/8/why-soft-skills-core-to-IT

168
translated/talk/20210216 What does being -technical- mean.md Normal file
View File

@ -0,0 +1,168 @@
[#]: collector: (lujun9972)
[#]: translator: (Chao-zhi)
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (What does being 'technical' mean?)
[#]: via: (https://opensource.com/article/21/2/what-technical)
[#]: author: (Dawn Parzych https://opensource.com/users/dawnparzych)
“技术”是什么意思？
======
用“技术”和“非技术”的标签对人们进行分类，会伤害个人和组织。本文作为本系列的第 1 篇，将阐述这个问题。
![question mark in chalk][1]
“技术”一词描述了许多项目和学科：**技术**淘汰赛、**技术性**犯规、攀岩比赛的**技术**课程和花样滑冰运动的**技术**得分。广受欢迎的烹饪节目 “_The Great British Bake-Off_” 包括一个“烘焙**技术**挑战”。任何参加过剧院演出的人都可能熟悉**技术**周，即戏剧或音乐剧首演前的一周。
如您所见，**技术**一词并不严格适用于软件工程和软件操作，所以当我们称一个人或一个角色为“技术”时，我们的意思是什么，为什么使用这个术语？
在我 20 年的科技生涯中，这些问题引起了我的兴趣，所以我决定通过一系列的采访来探讨这个问题。我不是工程师，也不写代码，但这并不意味着我是**非技术性**的。但我经常被贴上这样的标签。我认为自己是**技术性**的，通过这个系列，我希望你会明白为什么。
我知道我不是一个人。群众讨论是很重要的，因为如何定义和看待一个人或一个角色会影响他们做好工作的信心和能力。如果他们感到被压垮或不受尊重，就会降低他们的工作质量，挤压创新和新思想。你看，这一切都是循序渐进的，那么我们怎样才能改善这种状况呢？
我首先采访了 7 个不同角色的人。
在本系列中，我将探讨“技术”一词背后的含义、技术的连续性、将人分类为技术性或非技术性的意外副作用，以及通常被认为是非技术性的技术角色。
### 定义技术和非技术
首先，我们需要做个名词解释。根据字典网，“技术/技术性的”是一个具有多重含义的形容词，包括：
* 属于或关于艺术、科学等学科的
* 精通或熟悉某一特定的艺术或行业
* 技术要求高或困难（通常用于体育或艺术）
而“非技术性”一词在科技公司中经常被用来描述非工程人员。但是“非技术性”的定义是“与某一特定活动领域及其术语无关、不具有该领域的特征或不精通该领域”。
作为一个写作和谈论技术的人，我认为自己是技术型的。如果你不熟悉这个领域和术语，就不可能书写或谈论一个技术主题。有了这种理解，每个从事技术工作的人都是技术人员。
### 为什么要分配标签？
那么，为什么划分技术与非技术？这在技术领域有什么意义呢？我们试图通过分配这些标签来实现什么？有没有一个好的理由？而我们有没有重新评估这些理由？让我们讨论一下。
当我听到人们谈论技术人员和非技术人员时，我不禁想起 Seuss 教授写的童话故事 [_The Sneetches_][2]。Sneetches 的肚子上有没有星星被演化为一种渴望。Sneetches 们进入了一个无限循环，试图达到正确的状态。
标签可以起到一定的作用，但当它们迫使一个群体的等级被视为比另一个更好时，它们就会变得危险。想想你的组织或部门：销售、资源、营销 、QA、 工程等，哪一组的在重要性上高于或低于另一组？
即使它不是直接说的或写在什么地方，也可能是被人们默认的。这些等级划分通常也存在于规章制度中。技术内容经理利兹•哈里斯 （Liz Harris） 表示，在技术写作界存在着一个技术含量的评级，你越是偏技术的文章，你得到的报酬就越高，而且往往在技术写作社区里你得到的关注就越多。”
术语“技术”通常用于指一个人在某一主题上的深度或专业知识水平。销售人员也有可能会要求需要懂技术以更好的帮助客户。从事技术工作的人，他们是技术性的，但是也许更专业的技术人员才能胜任这个项目。因此，请求技术支援可能是含糊不清的表述。你需要一个对产品有深入了解的人吗？您是需要一位了解基础架构堆栈的人员？或者有人写下如何配置 API 的步骤？
我们应该要把技术能力看作是一个连续函数，而不是把人简单的看作技术性的或非技术性的。这是什么意思？开发人员关系主管 Mary thengwall 描述了她如何对特定角色所需的不同深度的技术知识进行分类。例如，项目可能需要开发人员、具有开发人员经验背景的人员或精通技术的人员。反而正是那些精通技术的人经常被贴上非技术的标签。
根据 Mary 的说法，如果“你能解释（一个技术性的）话题，你知道你对产品的看法，你知道该说什么和不该说什么的基本知识，那么你就是技术高手。你不必有技术背景，但你需要知道高级技术信息，然后还要知道向谁提供更多信息。”
### 标签带来的问题
当我们使用标签来具体说明我们需要完成一项工作时，它们可能会很有帮助，比如“开发人员”、“有开发人员背景”和“技术达人”。但是当我们使用标签的范围太广时，将人们分为两组中的一组可能会产生“弱于”和“优于”的感觉
当一个标签成为现实时，无论是有意还是无意，我们都必须审视自己，重新评估自己的措辞、标签和意图。
高级产品经理 Leon Stigter 提出了他的观点：“作为一个集体行业，我们正在构建更多的技术，让每个人都更容易参与。如果我们对每个人说：‘你不是技术型的’，或者说：‘你是技术型的’，然后把他们分成几个小组，那些被贴上非技术型标签的人可能永远不会去想：‘其实我自己就能完成这个项目’，实际上，我们需要所有这些人真正思考我们行业和社区的发展方向，我认为每一个人类都应该有这个主观能动性。”
#### 身份
如果我们把我们的身份贴在一个标签上，当我们认为这个标签不再适用时会发生什么？当 Adam Gordon Bell 从一个开发人员转变为一个管理人员时，他很挣扎，因为他总是认为自己是技术人员，而作为一个管理人员，这些技术技能没有被使用。他觉得自己不再有价值了。编写代码并不能提供比帮助团队成员发展事业或确保项目按时交付更大的价值。所有角色都有价值，因为它们都是确保商品和服务的创建、执行和交付所必需的。
“我想我成为一名经理的原因是我们有一支非常聪明的团队和很多非常有技能的人，但是我们并不总是能完成最出色的工作。所以技术不是限制因素，对吧？”亚当说：“我想通常不是技术限制了团队的发挥”。
Leon Stigter 说，让人们一起合作并完成令人惊叹的工作的能力是一项很有价值的技能，不应低于技术角色的价值。
#### 自信
[负担症候群 ][3] 是指无法认识到自己的能力和知识，从而导致信心下降，以及完成工作和做好工作的能力下降。当你申请在会议上发言，向科技刊物提交文章，或申请工作时，负担症候群就会发作。负担症候群是一种微小的声音，它说：
* “我技术不够胜任这个角色。”
* “我认识更多的技术人员，他们在演讲中会做得更好。”
* “我在市场部工作，所以我无法为 Opensource.com 这样的技术网站写文章。”
当你把某人或你自己贴上非技术性标签的时候，这些声音就会变得更响亮。这很容易导致在会议上听不到新的声音或失去团队中的人才。
#### 刻板印象
当你认为某人是技术人员时，你会看到什么样的印象？他们穿什么？他们还有什么特点？他们是外向健谈，还是害羞安静？
Shailvi Wakhlu 是一位高级数据总监，她的职业生涯始于软件工程师，并过渡到数据和分析领域。“当我是一名软件工程师的时候，很多人都认为我不太懂技术，因为我很健谈，很明显这就意味着你不懂技术。他们认为你不孤独的待在角落就是不懂技术。”她说。
我们对谁是技术型与非技术型的刻板印象会影响招聘决策，或者我们的社区是否具有包容性。你也可能冒犯别人，甚至是能够帮助你的人。几年前，我在某个摊位上工作，问别人我能不能帮他们。“我要找最专业的人帮忙”他回答说。然后他就出发去寻找他的问题的答案。几分钟后，摊位上的销售代表和那位先生走到我跟前说：“Dawn，你是回答这个人问题的最佳人选。”
#### 污名化
随着时间的推移，我们夸大了“技术”技能的重要性，这导致了“非技术”的标签被贬义地使用。随着技术的蓬勃发展，编程人员的价值也随之增加，因为这种技能为市场带来了新产品和新的商业方式，并直接帮助了盈利。然而，现在我们看到人们故意将技术角色凌驾于非技术角色之上，阻碍了公司的发展和成功。
人际交往技能通常被称为非技术技能。然而，它们有着高度的技术性，比如提供如何完成一项任务的分步指导，或者确定最合适的词语来传达信息或观点。这些技能也至关重要的影响你的工作能否取得成功。
**[Read next: [Goodbye soft skills，hello core skills: Why IT must rebrand this critical competency][4]]**
通读《城市词典》上的文章和定义，难怪人们会觉得自己的标签有道理，而其他人会患上负担症候群，或者觉得自己失去了身份。在线搜索时，城市词典定义通常出现在搜索结果的顶部。这个网站大约 20 年前开始是一个定义俚语、文化表达和其他术语的众包词典，现在变成了一个充满敌意和负面定义的网站。
这里有几个例子：城市词典将非技术经理定义为“不知道他们管理的人应该做什么的人”
提供如何与“非技术”人员交谈技巧的文章包括以下短语：
* “如果我抗争，非技术人员究竟是如何应对的？”
* “在当今的职业专业人士中，开发人员和工程师拥有一些最令人印象深刻的技能，这些技能是由多年的技术培训和实际经验磨练而成的。”
这些句子意味着非工程师是低人一等的，他们多年的训练和现实世界的经验在某种程度上没有那么令人印象深刻。对于这样的说辞，我可以举一个反例：Therese Eberhard。她的工作被许多人认为是非技术性的。她是个风景画家。她为电影和戏剧画道具和风景。她的工作是确保像甘道夫的手杖这样的道具看起来栩栩如生，而不是像塑料玩具。要想在这个角色上取得成功，需要有很多解决问题和实验化学反应的方法。Therese 在多年的实战经验中磨练了这些技能，对我来说，这相当令人印象深刻。
#### 守门人行为
使用标签会设置障碍，并导致守门人行为，这决定谁可以进入我们的组织，我们的团队，我们的社区。
据一位开源开发者 Eddie Jaoude 所说，“技术”、“开发人员”或“测试人员”的头衔在不应该出现的地方制造了障碍或权威。我们应该将重点放在谁能为团队或项目增加价值，而头衔是无关紧要的。”
如果我们把每个人看作一个团队成员，他们应该以这样或那样的方式贡献价值，而不是看他们是否编写文档、测试用例或代码，那么我们将根据真正重要的东西来重视他们，并创建一个能完成惊人工作的团队。如果测试工程师想学习编写代码，或者程序员想学习如何在活动中与人交谈，为什么要设置障碍来阻止这种增长？拥抱团队成员学习、改变和向任何方向发展的渴望，为团队和公司的使命服务。
如果有人在某个角色上失败了，与其把他们说成“技术不够”，不如去看看问题到底是什么。你是否需要一个精通 JavaScript 的人，而这个人是另一种编程语言的专家？并不是说它们不专业。技能和知识不匹配。你需要合适的人来扮演合适的角色。如果你强迫一个精通业务分析和编写验收标准的人去编写自动化测试用例，他们就会失败。
### 如何取消标签
如果你已经准备好改变你对技术性和非技术性标签的看法，这里有帮助你改变的提示。
#### 寻找替代词
我问我采访过的每个人，我们可以用什么词来代替技术性和非技术性。没有人回答！我认为这里的挑战是我们不能把它归结为一个词。要替换术语，你需要使用更多的词。正如我之前写的，我们需要做的是变得更加具体。
你说过或听到过多少次这样的话：
* “我正在为这个项目寻找技术资源。”
* “那个候选人技术不够。”
* “我们的软件是为非技术用户设计的。”
技术性和非技术性词语的这些用法是模糊的，不能表达它们的全部含义。更真实、更详细地了解您的需求那么您应该说：
* “我想找一个对如何配置 Kubernetes 有深入了解的人。”
* “那个候选人对 Go 的了解不够深入。”
* “我们的软件是为销售和营销团队设计的。”
#### 拥抱成长心态
知识和技能不是天生的。它们是经过数小时或数年的实践和经验形成的。认为“我只是技术不够”或“我不能学习如何做营销”反映了一种固定的心态。你可以向任何你想发展的方向学习技能。列一张清单，列出你认为是技术性的技能，或非技术性的技能，但要具体（如上面的清单）。
#### 认可每个人的贡献
如果你在科技行业工作，你就是技术人员。在一个项目或公司的成功中，每个人都有自己的作用。与所有做出贡献的人分享荣誉，而不仅仅是少数人。认识提出新功能的产品经理，而不仅仅是开发新功能的工程师。认识一个作家，他的文章在你的公司迅速传播并产生了新的线索。认识在数据中发现新模式的数据分析师。
### 下一步
在本系列的下一篇文章中，我将探讨技术中经常被标记为“非技术”的非工程角色
--------------------------------------------------------------------------------
via: https://opensource.com/article/21/2/what-technical
作者：[Dawn Parzych][a]
选题：[lujun9972][b]
译者：[Chao-zhi](https://github.com/Chao-zhi)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/dawnparzych
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/question-mark_chalkboard.jpg?itok=DaG4tje9 (question mark in chalk)
[2]: https://en.wikipedia.org/wiki/The_Sneetches_and_Other_Stories
[3]: https://opensource.com/business/15/9/tips-avoiding-impostor-syndrome
[4]: https://enterprisersproject.com/article/2019/8/why-soft-skills-core-to-IT