公司对软件开发人员基本要求
Smart developers are rare these days. Their efficiency is almost three times that of the typical programmer and ten times the mediocre programmer. The upper 1% of software developers not only write concrete code, but they also have valuable intangible features.
如今，聪明的开发人员很少见。 它们的效率几乎是普通程序员的三倍，是普通程序员的十倍 。 高1％的软件开发人员不仅编写具体的代码，而且还具有有价值的无形功能。
“The best programmers are up to 28 times better than the worst programmers.” — Robert L. Glass
“最好的程序员比最差的程序员高28倍。” —罗伯特·格拉斯
That’s precisely why we’re going to go over this list of essential programming qualities that I think make you a smart developer.
这就是为什么我们要仔细研究一下我认为可以使您成为聪明的开发人员的这些基本编程质量的原因。
＃1：建设性心态 (#1: Constructive Mindset)
A smart developer minds the performance of the project: they are constructive, go the extra mile to finish the work, and give their utmost daily.
精明的开发人员会关注项目的绩效：他们具有建设性，要付出更多努力才能完成工作，并每天付出最大的努力。
While developers mustn’t overwhelm themselves with repeated critical timelines, crunch time is sometimes inevitable.
尽管开发人员一定不会因重复的关键时间表而感到不知所措，但有时紧缩时间是不可避免的。
Whenever you require to market a product or have to deliver a few functionalities for a cutoff date, a smart developer will step up and bring the product whenever needed because they value it. A successful developer won’t allow their pride to get in the way of critical feedback.
每当您需要销售产品或必须提供一些功能作为截止日期时，精明的开发人员都会加紧并在需要时带来产品，因为他们重视产品。 一个成功的开发人员不会让他们的骄傲阻碍关键的反馈。
＃2：再也不会重复 (#2: Never Repeat It Again)
You have reached the point where you look at a piece of code and think more than once, “well, this code style appears the same as any code I wrote in the past.”
您已经达到了查看一段代码并思考不止一次的地步，“好吧，这种代码样式看起来与我过去编写的任何代码相同。”
This was meant to ring a bell. Since this is a condition, you want to prevent it. Duplicate code is horrible to make your code smell. Code is more difficult to maintain as changes to this code must be made in many areas. This makes it easier for bugs to sneak into the code.
这是想敲响钟声。 由于这是一个条件，因此您要防止它。 重复的代码会使您的代码闻起来很恐怖。 维护代码更加困难，因为必须在许多领域中对此代码进行更改。 这使得错误更容易潜入代码中。
The DRY (don’t repeat yourself) theory is considered a healthy idea. This means you should probably refactor your code when you start typing the same code. Divide your code and logic into smaller units and use it by calling it wherever you want.
DRY(不要重复自己)理论被认为是健康的想法。 这意味着当您开始键入相同的代码时，您可能应该重构代码。 将您的代码和逻辑划分为较小的单元，并通过在任意位置调用它来使用它。
＃3：感觉完结后进行重组 (#3: Restructure When You Feel You’re Finished)
Some developers, particularly with no or little knowledge, believe their work is finished as soon as their code is working as expected. But the word “finished” does not just include writing a set of code for a great attribute.
一些开发人员，尤其是一无所知的开发人员，认为他们的代码按预期工作后就可以完成工作。 但是，“完成”一词不仅包括为出色的属性编写一组代码。
The code is working, correct? What’s the point, then?
该代码有效，对吗？ 那有什么意义呢？
Yeah, you’re right. But you may not have produced the cleanest piece of code you’ve ever written. Some things may be clear to you, but how will other programmers feel when they look at your code? Be critical of it.
是啊，你说得对。 但是您可能还没有编写出您编写过的最干净的代码。 有些事情可能对您很清楚，但是其他程序员在查看您的代码时会有什么感觉？ 批评它。
Smart developers restructure the code without changing its external behaviors before they get to the next task. It is called code refactoring.
精明的开发人员在进行下一个任务之前，无需更改其外部行为即可重组代码。 这称为代码重构 。
Potential advantages of code refactoring may include improved code readability and reduced complexity; these can improve the source code’s maintainability and create a simpler and cleaner code. Refactoring the code will pay for itself in the long run.
代码重构的潜在优势可能包括提高代码的可读性和降低复杂性。 这些可以改善源代码的可维护性，并创建更简单，更简洁的代码。 从长远来看，重构代码可以收回成本。
＃4：更加重视业务 (#4: Pay More Attention to the Business)
Good developers seem to concentrate too much on mastering the technology stack that the business is out of vision. It is essential to consider the business on your track towards being an expert of your software platform. Smart programmers always keep why they are creating it in mind.
优秀的开发人员似乎过于专注于掌握业务无法实现的技术堆栈。 考虑成为您的软件平台专家的企业，必不可少。 聪明的程序员始终牢记创建它们的原因。
Good developers focus on their job’s technical matters only. They do not really talk about the business or the economic factors justifying the existence of their tasks.
优秀的开发人员仅关注其工作的技术问题。 他们并没有真正谈论证明其任务存在的商业或经济因素。
Smart developers create value for the business and don’t spend too much time on something that doesn’t matter.
精明的开发人员可以为企业创造价值，并且不会在不必要的事情上花费太多时间。
＃5：次要承诺 (#5: Minor Commitments)
Smart developers don’t make big commitments because such can have several adverse effects. Since so much stuff change in the commit, what really changed is unknown.
聪明的开发人员不会做出重大承诺，因为这可能会产生多种不利影响。 由于提交中发生了很多更改，因此真正更改的是未知的。
Because what about the person who will review the program? The reviewer will be afraid to merge the program as so many items to combine may be likely to break the code.
因为要审核程序的人呢？ 审阅者会害怕合并程序，因为要合并的项目太多可能会破坏代码。
Minor commitments allow the developer to send a brief commit message.
次要承诺允许开发人员发送简短的提交消息。
When you have spotted the commit in which the issue was found, you don’t have much code that might have created this issue, as the commit is small and it is simpler to fix.
发现发现问题的提交后，由于该提交很小且更易于修复，因此您可能没有太多的代码可能会造成此问题。
Code reviews with small commits get much more accessible. They allow one change to be reviewed at a time, enabling the reviewers to understand what is actually happening.
少量提交的代码审查变得更加容易访问。 它们允许一次审核一项更改，从而使审阅者能够了解实际发生的情况。
＃6：连贯性至关重要 (#6: Coherence Is Vitally Important)
Do you prefer to use spaces rather than tabs? Fantastic! Everything you do in your program, do it regularly, at least.
您更喜欢使用空格而不是制表符吗？ 太棒了！ 您在程序中所做的一切，至少要定期进行。
The issue of becoming unreliable is the inevitable fact that time ruins software. The longer a section of a program exists, the more people work on it, the more confusion arises.
变得不可靠的问题是时间毁了软件的必然事实。 一个程序的一部分存在的时间越长，工作的人就越多，那么混乱就越多。
So what can smart developers do to be more coherent?
那么，聪明的开发人员可以做些什么来使其更加协调一致？
Smart developers understand that coherence has a significant effect on the codebase’s usability
精明的开发人员了解一致性对代码库的可用性有重要影响
They choose a style guide as one of the first things and stick to it when they have their style guide. They can use a linter to test the code for style problems. Additionally, they use the names of classes, variables, and methods in a similar way.
他们选择样式指南作为第一件事，并在拥有样式指南时坚持使用。 他们可以使用linter来测试代码中的样式问题。 此外，它们以类似的方式使用类，变量和方法的名称。
＃7：快速学习能力 (#7: Quick Learning Aptitude)
Smart developers are generally incredible self-learners. They can learn new languages and technologies swiftly and often do so outside of the job for personal values. They can process information and make flying connections.
聪明的开发人员通常是不可思议的自学者。 他们可以快速学习新的语言和技术，并且经常在工作之外学习个人价值。 他们可以处理信息并建立飞行联系。
Each developer encounters a circumstance in which they do not know the solution; great developers create numerous tools, interact with the proper person, and explore whatever approach. Everybody’s biggest asset is knowing how to learn, and brilliant developers have acquired the ability to discover themselves.
每个开发人员都会遇到他们不知道解决方案的情况； 优秀的开发人员可以创建大量工具，与合适的人互动，并探索任何方法。 每个人的最大资产就是知道如何学习，而杰出的开发人员已经具备了发现自己的能力。
＃8：连接一次 (#8: Connect It Once)
I’m going to correct it afterward. Yeah, we’ve all heard that before. Because we all know how many “later” problems have been resolved. You’re right. Never. Whenever you see a TODO or FIXME comments, you know that the code is likely sitting unmonitored and forgotten in your team or organization’s source code.
我将在以后纠正它。 是的，我们之前都听说过。 因为我们都知道已经解决了多少个“后期”问题。 你是对的。 决不。 每当您看到TODO或FIXME注释时，您就会知道该代码很可能不受监控，并被团队或组织的源代码遗忘。
Smart developers work on an application or user story from scratch until it is complete.
精明的开发人员从头开始处理应用程序或用户故事，直到完成为止。
This completion means that the code is restructuring for the beginning, just like we thought about before. Also, the code must be tested. And testing is likely the least favorite part of most developers’ jobs. But testing is far more than merely clicking on the easy route. Smart developers do screening as well as check other specific conditions too.
就像我们之前考虑的那样，这种完成意味着代码从头开始进行重组。 另外，必须对代码进行测试。 测试可能是大多数开发人员工作中最不喜欢的部分。 但是测试不仅仅是单击简单的路线。 精明的开发人员还会进行筛选以及检查其他特定条件。
＃9：一定不要停止改进 (#9: Must Not Stop Improving)
Every day, technological developments arise. And it could sometimes seem challenging to suit all the latest trends. Smart developers never stop improving because the day you stop improving is also the day you stop growing.
每天都有技术发展。 适应所有最新趋势有时似乎具有挑战性。 聪明的开发人员永远不会停止改进，因为停止改进的一天也是停止增长的一天。
The only way of staying meaningful is to learn new skills in today’s fast-changing technological world in which we live.
保持有意义的唯一方法是在我们赖以生存的当今瞬息万变的技术世界中学习新技能。
“Undertake something that is difficult; it will do you good. Unless you try to do something beyond what you have already mastered, you will never grow.’’ — Ronald E. Osborn
“从事困难的事情； 这对你有好处。 除非您尝试做一些超出您已掌握的知识的事情，否则您将永远无法成长。” –罗纳德·奥斯本(Ronald E. Osborn)
底线 (The Bottom Line)
Everybody has programming traits. Either productive or non-productive. Yet you can increase your productivity significantly and become a smart developer when you start to follow the appropriate programming qualities. The above essential attributes will not only impact you but also will most likely affect people around you.
每个人都有编程特质。 生产性的或非生产性的。 但是，当您开始遵循适当的编程质量时，您可以显着提高生产率并成为一个聪明的开发人员。 上述基本属性不仅会影响您，而且很可能会影响您周围的人。
“The fact is, you don’t break a bad habit; you substitute it with a new one.” — Denis Waitley
“事实是，你没有坏习惯； 您可以用新的替代它。” —丹尼斯·怀特利
公司对软件开发人员基本要求
4987
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
