You can be good at effective learning, to invest all free time into self-education, but it won’t make any result in your efficiency. Efficiency is the ratio of effort and money spent by you and for you to achieve a satisfactory result.
Explains: You solve the task qualitatively and in time, looking for the solution independently. You generate ideas that help colleagues to cope with their work. You are responsible for additional administrative and technical resources ("And let the techlid explain me personally, I was late for the stand-up", "I need a second SSD, colleague the next table has four of them"). Your word always has a weight. Your presence in the team raises the overall performance. It’s easy, pleasantly and safely to operate with you. You are effective.
This is how much your technical skills are good. If it’s possible for you to resolve 9 tasks from 10 then your performance is 0.9 (a high but not perfect).
How without it? The developer who can’t clearly convey his idea to a colleague fails as a team player. A particularly required skill is fluency in foreign languages communication. "You don't know what to do? Have some free time? Learn the language" — this advice is always relevant.
Said — did. In this issue, there shouldn’t be any compromise. The ability to rely on the word of colleagues — doesn’t worth it. Believe, the professional simply does not have the right to be a chatterbox. This quality is good to increase your significance and value in the eyes as an ordinary member of the team and your supervisor.
Demonstrate the desire and ability to develop. Of course, it’s impossible without a sincere interest in the job you do. Don't be afraid to take risks, applying new technologies to the project. Let the initiative come from you. Of course, your proposal should be deliberated and prudent. Nobody likes the loudmouths.
So, in my opinion, these are the basic qualities of any team player. Anyway, all they define professionalism and the market price. Of course, the final result of the assessment is affected by much more factors. I have listed only those which depend on you personally.
Here are 2 more paragraphs, if you’re a project manager
The factors listed above — this is just what concerns the developer. Project Manager — a little bit different story. But there are two points which show the high professionalism:
Ability to keep in touch with the team always:
In practice, it means that you, as a leader, have to create the trust and unity atmosphere. Often, our colleague’s personal problems do not care you until the word "at all". The consequence of this may be the situation when suddenly you won’t have a developer anymore, but with a hole on the project. And it will happen for objective reasons (illness, divorce, mother-in-law arrive, cat’s illness). But you’ll just learn about it as a matter of fact.
Especially stand the health problems. It’s not a secret for anybody that in our companies attitude to the working conditions organization is really far from the scientific.
Ability to give the opportunity to study:
Try to combine roles on the project in such way that the experienced developer would be able to teach the beginner. Everything is simple and difficult at the same time in here. It’s easy when both parties (student and, call it so, a mentor) are interested in such an educational format. But sometimes the mentor search approach. Here can be some difficulties. As a rule, the extra work is useless. Moreover, an experienced developer is unenthusiastic about the perspective to teach somebody, especially during his free time. We need to seek the individual approach. For example, to offer the task implementation using the new perspective tool. Sometimes an experienced colleague makes a recommendation for employment in the company to his friend or acquaintance. The company receives a new "fighter". The one who recommended and the one recommended, get on one project. Excellent relations "mentor-student" added.
All these points may seem obvious. But even the obvious must be repeated. Again and again.
To avoid any questions about "why I don't want to be paid more, I have mastered a lot of frameworks on my leisure (but filling up the current project)?" or "why do they make me the comments, the project is completed in time (with a terrible atmosphere in the team, half of which thought of resignation)?"
A Sober assessment of their own effectiveness as a professional helps to determine adequately the value of their work in the labour market. And to suggest the direction for growth.