Wolf and Husky, programmer and code-programmer, programming-IT information
IT news Editor's Note: this article is referred to in the "code" is exclusive in this paper refers to, is not the traditional sense of the concept, so if there are irregularities, please forgive me.
Wolves are real predators in nature, while the Huskies only human playthings. Looks exactly like the two, just as the Programmer of the IT sector (programmers) and the Coder (code rural). If the Wolf and Husky to metaphor the two occupations, real wolves Programmer is the software industry.
First, "Husky" habits
? They write code that a machine can understand.
? Code relies on the comments they read.
? They are only working time writing code.
? They do not like reading, but will occasionally see videos.
? They just reading other people's blogs, she never wrote.
? Their concerns is just progress.
? They just copied code.
? Problems they would ask their peers.
They always thought he would be a lot, like to use vast amounts of "proficient" to burnish their resumes, pretended to be the master.
? They are wrecked in C+V in an endless loop, and constantly complained that requirements change.
? That they will learn a code writing, and arrogant.
? They passively accepted the demand, while complaining about the unreasonable demand.
? They do not check their code before testing exposes defects, they are often difficult to find.
? They do not consider themselves responsible for code quality, it should be the Manager and test things.
? They will directly get the task began to work.
? They often have a phobia of the document.
? They do not worship the professionals.
? They are good at buck.
? They are not ignore compilation warnings dispose of.
? They can just write a running program.
? They put off an unpleasant task.
? They are more likely to give up their designs.
? Their programming often stop at the coded representation.
Second, the "Wolf" habits
? They write code that people can read.
? Uniform style and has their code self-describing.
? They work not only in time, will also write the code in their spare time.
? They will look at a lot of books, read a lot of technical information and, of course, will watch the video.
? Not only do they read other people's blogs, they themselves would be blogging, they think that sharing knowledge is happiness.
? They are not only concerned about progress and more concerned about the quality of the code, provided real progress of the programme, in front of the boss sticks to his views.
? They reuse code instead of the code.
? Problems they were trying to solve, visiting communities, before asking Companion.
They always think they can do better, and sincerely admire those giants, not the master does not pretend to master.
? They often thinks how to decouple, smart design respond to unexpected changes.
? When mastering a code writing, what they see is often deep-seated problems behind, and professional standards.
? They will say no to unreasonable demands, and work to try to influence their leaders.
? They will refactor their own code, defects and maintain your own checklist.
? Improving code quality they think is their own responsibility, and take responsibility for their negligence.
? After they got the task, before the action, analysis and planning, rather than coding right away.
? They tend to read project documentation.
They and those who wish to improve their software development skills, attend the forums, join a community to participate in technical discussions.
? They admit their mistakes.
? Warnings and errors they be treated equally.
? They build a thorough understanding of the program.
? They will be an unpleasant task that is honed to itself.
? They tend to stick to their design.
? Their programming language, touch.
Third, the "Wolf" or "Siberian Husky"?
Wolf and Husky metaphor means overcome Programmer Coder in the technology field, but the reality is often more popular Coder, as the Huskies more likeable. The reason is simple, Programmer in numerous Coder is out of place. Programmer to complete tasks faster and more efficiently, they hate working overtime against inefficient processes, they believe in their ability and often stick to their views, say no to unreasonable demands. This, in the eyes of employers is treason. Coder quiet a lot, they are willing to work overtime, on designing no comments, will not say no to demand, a problem they said, this is someone else's problem. Both codes, in the layman's view there is no difference. In the eyes of employers, often those who shut up overtime should be reused.
Perhaps the Programmer does not want to allow yourself to be isolated, but the reality is cruel. Lack of tolerance, friendly reminder, may also be regarded as showing off, is a challenge to authority. Wolves in the Wolf alone, to get a sense of their own identity. Software Builder is a Programmer and not a Coder. If you are a Wolf, and you feel the sense of team identity, you may wish to change the environment because, playing chess and bad chess basket, never progress .
If you are an enlightened leader, when you read this article, I really hope you will take note of those "barbed" employees, as is likely, he is better than everyone else in your team even further.
If you are a programmer, then you choose what Wolf or a Husky. Wolf could not live peacefully, without big lunch, but it has great power, freedom, and dignity.
狼与哈士奇，
程序员和码农 -
程序员,编程 - IT资讯
IT资讯编者按：本文中提到的“码农”属于文中专属指代，并非传统意义上的概念，因此若有处理不妥之处，还请见谅。
狼是自然界中真正的掠食者，而哈士奇不过是人类的玩物。两者长得确实很像，就如同IT界的Programmer（程序员）和Coder（码农）。如果用狼和哈士奇来隐喻这两种职业，Programmer无疑是软件业真正的狼。
一、“哈士奇”的习性
• 他们写出机器可以理解的代码。
• 他们的代码依靠注释读懂。
• 他们只在工作时间写代码。
• 他们不喜欢看书，但偶尔会看看视频。
• 他们只会阅读别人的博客，自己从来不写。
• 他们关注的仅仅是进度。
• 他们仅仅是复制代码。
• 遇到问题他们会直接问同伴。
• 他们总是认为自己会的很多，喜欢用海量的“精通”来装点自己的简历，假装高手。
• 他们每天沉寂在C+V的死循环中，并不断地抱怨需求变更。
• 他们会因为学会了某种代码的写法，而骄傲自满。
• 他们一边在被动地接受需求，一边在抱怨不合理的需求。
• 他们不会检查自己的代码，在测试暴露缺陷之前，他们往往难以发现。
• 他们不认为自己要为代码质量负责，那应该是管理者和测试的事情。
• 他们在拿到任务后会直接开始工作。
• 他们往往具有文档恐惧症。
• 他们并不崇拜专业人士。
• 他们擅长推卸责任。
• 他们对编译警告弃之不理。
• 他们只是在写可以运行的程序。
• 他们会拖延不喜欢的任务。
• 他们更容易放弃自己的设计。
• 他们的编程往往止步于编码的表象。
二、“狼”的习性
• 他们写出人可以读懂的代码。
• 他们的代码风格统一并具有自描述性。
• 他们不仅在工作时间，在业余时间也会写代码。
• 他们会看大量的书籍，阅读大量技术资料，当然也会看视频。
• 他们不仅阅读别人的博客，他们自己也会写博客，他们认为分享知识是快乐的。
• 他们不仅关注进度而且更关注代码的质量，提供现实的进度方案，在上司面前坚持自己的意见。
• 他们复用代码而不是复制代码。
• 遇到问题他们会尝试自己解决，访问社区，然后才会询问同伴。
• 他们总是认为自己还能做的更好，并对那些巨人由衷地敬佩，在不是高手时不假装高手。
• 他们经常在思索如何能够解耦，用灵动的设计应对突然到来的变更。
• 当掌握某种代码的写法，他们看到的往往是背后深层次的问题，并向专业水准看齐。
• 他们会对不合理的需求说不，并在工作中尝试影响他们的领导。
• 他们会经常重构自己的代码，并维护自己的缺陷核对表。
• 他们认为提高代码质量是自己的责任，并为自己的过失而负责。
• 他们在拿到任务后，会在行动之前，进行分析和计划，而不是马上编码。
• 他们往往会认真阅读项目文档。
• 他们和希望提高软件开发技能的人为伍，参加交流会，加入某个社区参与技术讨论。
• 他们敢于承认错误。
• 他们将警告与错误同等对待。
• 他们在构建自己彻底理解的程序。
• 他们将不喜欢的任务认为是对自身的磨砺。
• 他们往往坚持自己的设计。
• 他们的编程往往深入语言，触及思想。
三、做“狼”还是“哈士奇”？
狼和哈士奇的隐喻意味着Coder难以在技术实战中战胜Programmer，但现实是，往往Coder更受欢迎，如同哈士奇更讨人喜欢一样。原因很简单，Programmer在众多Coder之中显得格格不入。Programmer能更快更高效地完成任务，他们讨厌加班，抵制低效的流程，他们对自己的能力深信不疑，并经常坚持自己的意见，对不合理的需求说不。这些，在雇主的眼里就是叛逆。而Coder就低调很多，他们甘于加班，对设计没有意见，不会对需求说不，出了问题他们总在说，这是别人的问题。他们两者的代码，在外行看来没有差别。在雇主眼中，往往那些闭嘴加班的员工更应该重用。
也许，Programmer们并不想让自己被孤立，但现实却是残酷的。人们缺少包容，善意的提醒，也可能会被认为是卖弄，是对权威的挑战。狼只有在狼群中，才能得到自身的认同感。软件的构建者是Programmer而不是Coder。如果你是一匹狼，而你有感受不到团队的认同感，那你不妨换一换环境，因为，和臭棋篓子下棋，永远无法进步。
如果你是位开明的领导者，当你读到这篇文章时，我真切地希望你能留意那些“带刺”的员工，因为很可能，他比你团队中的其他人都看的更远。
如果你是名程序员，那么请你选择到底是做狼还是哈士奇。狼可能没有安稳的生活，没有丰盛的午餐，但却拥有强大的力量，自由，以及尊严。