Re: Ways to assess employee performance
To comment on the topic is a bit much, therefore, with your permission I will answer the topic.
Starting to read the article, I completely agreed on how it is impossible to evaluate the effectiveness, but having reached as much as possible, I became very disagree. What am I talking about? Look further ...
I will make a reservation right away, I do not want to say that these are poor evaluations of effectiveness. The main thing when applying these, or any other estimates, is not to get involved, otherwise the effect will be the opposite.
1. Less mistakes - more efficient employee.
This postulate puts forward the idea: a programmer who does not make mistakes (extrapolating requirements to fewer mistakes) is beneficial to the company. Tell you who does not make mistakes? (Well, if interested, then here ).
Now, let's look from an economic point of view. For example, you as developers implement a method of uploading a file to a web server. You checked the basic things: loading an empty file, downloading a small file, downloading a little more. And transferred to the testing department. Where the testing specialist checked how the form uploads a 2 GB file. It checks on channels 10Mb / s, 2 Mb / s, 1Mb / s, 0.5Mb / s. Tell me how long does it take? Add to this the test of disconnected communications, working out storage overflows and much more. Why am I? Yes, it’s all about the fact that you will pay a programmer 2-3 times more for testing than the person responsible only for testing. Yes, the programmer must conduct the white-box test! But a programmer who transcends reasonable boundaries in this matter is evil. By the way this also came to my mind [1]. Well, in conclusion, as soon as you start paying the programmer for the fact that he has few errors, he will agree with the tester, and they will share the bonus.
2. Idea generators are many times more effective than idea consumers
Here, it’s even a shame to answer ... Here it seems to you who is better for your company, a person who generates 100 ideas per hour, lights up with them, carries away with himself ... But also quickly cools and spills over following idea. Or an employee generating a year may have one worthwhile idea, but bringing it to fruition.
Well, “Because they are interested in reinventing bicycles, and in no case should they take this opportunity away from them. "- I don’t even know ... In a university, in a research center, in the testing department ... But a developer inventing bicycles as part of a commercial project, in most cases, is evil. [2]
3. The more abstract thinking, the more efficient the employee
I met a couple of times "architects" who turned a simple abstraction from two levels of inheritance into a hierarchy of level classes by 5-7. And do you really need it? I recommend reading [3].
4. The effectiveness of the employee is directly proportional to his self-motivation
Here I agree with self-motivation. This is the motivation that requires growing further. But with the conclusion about where to work ... I fundamentally disagree. The “aggressive” person, according to the author, seeks to work in a startup. That’s because everyone who reads this article seeks to broaden their horizons, to obtain new ideas, which may be contrary to your beliefs (that is, self-motivated), but ... There are two suggestions in front of you: to work in a startup (a site with a brilliant idea, from you it is required to develop MySql + Php) and in Intel (development of a compiler for a parallel programming language). Whose proposal do you accept? As another example, how a company with the letter G increases the level of self-motivation of its employees, present and future - [4].
5. The faster employees complete the code, the more efficient they are.
+1
Well, in conclusion:
Each person has a certain outlook. When this horizon narrows to infinitely small - it turns to a point. It is then that a person begins to say that this is his “point of view”. Edwin Gilbert
Therefore, read, compare, and make your decision, even if it turns out to be not always correct. Have a nice day, and effective programmers in colleagues and subordinates.
References
1. Victor435 . Software testing: how to explain to the manager that 2 x 2 = 4?
2. HighOctane . Ten Tips for Beginner Programmers Tip # 6
3. Joel Spolsky. Do not let Astronauts of Architecture intimidate you
4.http : //kitya.livejournal.com/188574.html
Starting to read the article, I completely agreed on how it is impossible to evaluate the effectiveness, but having reached as much as possible, I became very disagree. What am I talking about? Look further ...
I will make a reservation right away, I do not want to say that these are poor evaluations of effectiveness. The main thing when applying these, or any other estimates, is not to get involved, otherwise the effect will be the opposite.
1. Less mistakes - more efficient employee.
This postulate puts forward the idea: a programmer who does not make mistakes (extrapolating requirements to fewer mistakes) is beneficial to the company. Tell you who does not make mistakes? (Well, if interested, then here ).
Now, let's look from an economic point of view. For example, you as developers implement a method of uploading a file to a web server. You checked the basic things: loading an empty file, downloading a small file, downloading a little more. And transferred to the testing department. Where the testing specialist checked how the form uploads a 2 GB file. It checks on channels 10Mb / s, 2 Mb / s, 1Mb / s, 0.5Mb / s. Tell me how long does it take? Add to this the test of disconnected communications, working out storage overflows and much more. Why am I? Yes, it’s all about the fact that you will pay a programmer 2-3 times more for testing than the person responsible only for testing. Yes, the programmer must conduct the white-box test! But a programmer who transcends reasonable boundaries in this matter is evil. By the way this also came to my mind [1]. Well, in conclusion, as soon as you start paying the programmer for the fact that he has few errors, he will agree with the tester, and they will share the bonus.
2. Idea generators are many times more effective than idea consumers
Here, it’s even a shame to answer ... Here it seems to you who is better for your company, a person who generates 100 ideas per hour, lights up with them, carries away with himself ... But also quickly cools and spills over following idea. Or an employee generating a year may have one worthwhile idea, but bringing it to fruition.
Well, “Because they are interested in reinventing bicycles, and in no case should they take this opportunity away from them. "- I don’t even know ... In a university, in a research center, in the testing department ... But a developer inventing bicycles as part of a commercial project, in most cases, is evil. [2]
3. The more abstract thinking, the more efficient the employee
I met a couple of times "architects" who turned a simple abstraction from two levels of inheritance into a hierarchy of level classes by 5-7. And do you really need it? I recommend reading [3].
4. The effectiveness of the employee is directly proportional to his self-motivation
Here I agree with self-motivation. This is the motivation that requires growing further. But with the conclusion about where to work ... I fundamentally disagree. The “aggressive” person, according to the author, seeks to work in a startup. That’s because everyone who reads this article seeks to broaden their horizons, to obtain new ideas, which may be contrary to your beliefs (that is, self-motivated), but ... There are two suggestions in front of you: to work in a startup (a site with a brilliant idea, from you it is required to develop MySql + Php) and in Intel (development of a compiler for a parallel programming language). Whose proposal do you accept? As another example, how a company with the letter G increases the level of self-motivation of its employees, present and future - [4].
5. The faster employees complete the code, the more efficient they are.
+1
Well, in conclusion:
Each person has a certain outlook. When this horizon narrows to infinitely small - it turns to a point. It is then that a person begins to say that this is his “point of view”. Edwin Gilbert
Therefore, read, compare, and make your decision, even if it turns out to be not always correct. Have a nice day, and effective programmers in colleagues and subordinates.
References
1. Victor435 . Software testing: how to explain to the manager that 2 x 2 = 4?
2. HighOctane . Ten Tips for Beginner Programmers Tip # 6
3. Joel Spolsky. Do not let Astronauts of Architecture intimidate you
4.http : //kitya.livejournal.com/188574.html