Reproduced from: http://www.cnblogs.com/MeteorSeed/archive/2012/08/04/2621993.html
A wolf is a real prey in nature, and husky is just a human plaything. The two are indeed very similar, just like the programer and coder in the IT field. If you use Wolf and husky to represent these two occupations, programer is undoubtedly the real wolf in the software industry.
1. Habits of husky
- They write code that machines can understand.
- Their code can be understood through annotations.
- They only write code during working hours.
- They do not like reading books, but occasionally watch videos.
- They only read others' blogs and never write them.
- They only focus on the progress.
- They just copy the code.
- If you have any questions, they will directly ask their peers.
- They always think they will have a lot of skills, and they like to use a large number of "proficient" to decorate their resumes and pretend to be masters.
- Every day, they are quietly in the endless cycle of C + V and constantly complain about demand changes.
- They will be complacent because they have learned how to write some code.
- While passively accepting requests, they complain about unreasonable demands.
- They do not check their own code and are often hard to find before testing exposes defects.
- They do not think they are responsible for code quality. They should be managers and tests.
- After obtaining the task, they will start working directly.
- They often have document phobia.
- They do not worship professionals.
- They are good at shirking responsibility.
- They discard the compilation warning.
- They are only writing programs that can run.
- They will delay tasks they don't like.
- It is easier for them to give up their design.
- Their programming often stops at the representation of encoding.
Ii. Wolf's habits
- They write code that people can understand.
- Their code style is uniform and self-descriptive.
- They not only write code during working hours, but also in their spare time.
- They will read a lot of books, read a lot of technical materials, and certainly watch videos.
- They not only read others' blogs, but also write their own blogs. They think sharing knowledge is a pleasure.
- They not only pay attention to the progress but also the quality of the Code, provide realistic progress solutions, and stick to their opinions in front of their superiors.
- They reuse code instead of copying code.
- If they encounter problems, they will try to solve the problem by themselves, visit the community, and then ask their peers.
- They always think they can do better and admire those giants. They do not pretend to be masters when they are not masters.
- They often think about how to decouple and use smart design to cope with sudden changes.
- When mastering the writing of a certain code, they often see deep-seated problems behind them and look at them with professional standards.
- They will say no to unreasonable demands and try to influence their leadership at work.
- They often refactor their code and maintain their own defect checklist.
- They believe that it is their responsibility to improve the quality of code and take responsibility for their mistakes.
- After receiving the task, they will analyze and plan before the action, instead of coding immediately.
- They often carefully read the project documents.
- They work with people who want to improve their software development skills, participate in exchange meetings, and join a community to participate in technical discussions.
- They dare to admit mistakes.
- They treat warnings as errors.
- They are building programs that they fully understand.
- They think that they do not like the task to sharpen themselves.
- They often stick to their own design.
- Their programming often goes deep into the language and involves ideas.
Cool 3 or husky
The metaphor of Wolf and husky means coder cannot beat programer in technical practice, but the reality is that coder is often more popular, just like husky. The reason is simple. programer seems out of place among many coders. Programer can complete tasks faster and more efficiently. They hate working overtime and resist inefficient processes. They are confident in their own capabilities and often stick to their opinions and say no to unreasonable demands. These are rebellious in the eyes of employers. Coder has a much lower profile. They are willing to work overtime, have no opinions on the design, and will not say no to the demand. If something goes wrong, they always say that this is a problem of others. There is no difference in the code between the two. In the eyes of employers, employees who shut up and work overtime should reuse them more often.
Maybe, programer doesn't want to isolate themselves, but the reality is cruel. People lack an inclusive and kind reminder, which may also be regarded as a spoof and a challenge to authority. A wolf can gain his own sense of identity only in the Wolf group. The software builder is programer rather than coder. If you are a wolf and you cannot feel the sense of identity of the team, you may wish to change the environment, because you can never make progress when playing games with a skey.
If you are an enlightened leader, when you read this article, I really hope that you can pay attention to the employees who are "stabbed", because it is very likely that, he looks farther than others in your team.
If you are a programmer, please choose whether to be a wolf or husky. A wolf may not have a stable life or a rich lunch, but has powerful power, freedom, and dignity.
