Preface:
Core competencies was first proposed by Prahalad and Gary Hamel two professors, generally considered the core competitiveness, namely businesses or individuals compared to competitive advantages and core competencies difference in terms of competitors have,
It means your advantage, but the best is the unique advantage, which is the core competitiveness.
So the core competitiveness of programmers what is it? He is not like PM, operations, marketing so difficult assessment. A good programmer must have the following several capabilities:
1. programming skills
This is no doubt, as a programmer can write code, write high-quality code, can be said to be basic skills, left this like a tree without roots, without water, more useless talk. This can be in the company to learn and master, rich theoretical knowledge in private in his spare time, look at some open source, hands-on from imitation to try, again and again.
2. Analysis of problem-solving skills
In essence, the boss to ask you all to solve the problem, you can solve the problem, in order to realize your worth, pay only bargaining chip.
A project, a task, or a bug, can be seen as a question of whether you can quickly analyze the situation and find the root of the problem from the appearance, or to break down a large problem into smaller problems that can be processed and regulations in time to solve it, you can say that you consider important technical standards sole criterion.
As a developer, there is a learning atmosphere is particularly important with a circle of exchange, this is one of my iOS exchange group: 638 302 184, whether you are white or Daniel welcome to enter, share the interview experience, discuss techniques, we can talk about growing up! Hope that helps developers avoid detours.
The following information is available to download in the group file, click here to download
Training Approaches
(1) rich industry experience, you experience more, you will naturally know how to deal with, the saying goes, do not eat pork, pig run have not seen a thing, probably meant.
(2) There are a number of conscious learning methodology, a structured exercise their own thinking, not just to work on all aspects of life, all kind of useful. Recommended Reading Liu Peng, not "dark time", it is designed for programmers to write methodology, and he is also a programmer. Some regressed PM, basically do not touch the code, but to listen to his men say about the situation, or to quickly find the root knot, they can not do without thinking of experience and systems.
3. Good attitude
Different companies have different cultures, there is more value in values. And I thought for programmers, the most important attitude that they can not improvise. The average programmer after finding the problem, try the East West try to solve the problem on the line, but good programmer will not easily compromise, we will try to analyze the causes of the problem, the fundamental solution, even going see Linux kernel code is also necessary to find the root cause of the bug.
4. The self-learning ability
As we all know, the programmer is a bitter forced to vocational, technical update with each passing day, new generation of products based on more dollars monthly basis, do not learn how long?
Learn divided into two blocks
A technical knowledge of learning, including programming skills, basic principles, algorithms and knowledge structure is closely related to the work environment, is also worth special mention is to learn the classic open source code, which is the only way to become a master;
Another piece of product knowledge, dynamic learning industry, the domestic situation is generally better to write code or relatively long people, began with the team, if there is no accumulation in this area, it will be difficult, even if the single-minded to do another technique, learn more about Some also help to deepen the understanding of the requirements, functional, not a bad thing.
5. communication skills
Speaking and writing are important, for the novice to listen and speak particularly noteworthy.
Listening is said that a task down to hear clearly what the problem is, what the needs are, what the conditions, listen carefully before you start. That is to express structured, say clearly the ins and outs, that's clear thinking to solve the problem. Some programmers work for several years, even a more complex issue of how it is, are not clear, the East about the West a bit, little bit of logic are not, it is clear that his idea is confusing.
Here I would like to add two points: one is to ask, not clear we must ask, do not wear, in fact, you joined the company three days to do something, you're probably what level, what kind of thinking, your leadership a clear picture , equipment useless.
Another feedback, one thing led to explain to you, you have to give him feedback at critical nodes, telling him how to do, what the difficulties, the next step to prepare how to do, what support needs and so on. Do not wait for leaders to ask, just tell him you have any questions get it working, many boss on this case is hated, after doing things like this twice, basically not very critical task will be yours.
6. continue summarized
On an issue, a class of problems, as well as different types of questions, good collate, and constantly reflect on their own problems, not even a bug in the code, you go through a period of time to look back, there are a lot of thinking is incorrect unreasonable, there are a lot of optimization point, if you feel that your code has been regressed, no flaws, you must be standing still, no progress.
Work experience required over time, but some people working for three years on those who work beyond 10 years of work experience and do not represent your ability to work, only continue to enhance their core competitiveness in order to be in a critical position in the company, salary to grow rapidly.
Programmers story
Story one: the ability is fundamental
Engineer: programmer, network client XXX broken. I now have a lot of things on hand to handle, however, you help solve the customer's problem.
Programmers: the amount, the customer is what causes disconnection, ah I want to how to troubleshoot ah??
engineer:……
PS: I know what causes disconnection, it also requires you to troubleshoot the network is disconnected, and how to troubleshoot you do not know what you do not know Xianxiang customers to understand the network environment, you do not know what topology it will not ping the gateway???? wireshark port packet capture it?
Story Two: to be a proactive person
Programmers: Manager ah, customers say here and now to increase the functionality of a historical curve inquiry, how do you see it?
Product Manager: ......
The correct approach should be: ah manager, client side said to increase the functionality of a historical curve inquiry, I carefully thought for a moment, about the design of two implementations. Option One: XXX, Option II: YYY. Do you think these two programs which is better, or if you have any other options?
PS: Do not think you're a programmer, only need to implement the code responsible for the design has nothing to do with who you do not want to have such a subordinate!. When your boss really tired!
Story Three: EQ is very important
Manager: This is how the interface does not show anything, it is given?
iOS programmers: they must be back there again which program to write the configuration file is broken, leading to interface to read configuration error.
PS: the program has a bug no big deal, you do not always put the problem onto others ah. You say, background development brothers to lay the gun, and offend a bunch of people. And managers impression of you will not be good to go instead?
At last
Hope of this paper has some reference value of learning for everyone!
Scan code into the exchange group, there are techniques to chat, no technology to learn
