How do managers know if a person is a good or a bad programmer?
Posted
by
Pavel Shved
on Programmers
See other posts from Programmers
or by Pavel Shved
Published on 2011-03-07T20:29:49Z
Indexed on
2011/03/08
0:18 UTC
Read the original article
Hit count: 415
management
|evaluation
In most companies that do programming teams and divisions consist of programmers who design and write code and managers who... well, do the management stuff. Aside from just not writing code, managers usually do not even look at the code the team develops, and may even have no proper IDE installed on their work machines.
Still, the managers are to judge if a person works well, if he or she should be put in charge of something, or if particular developer should be assigned to a task of the most importance and responsibility. And last, but not least: the managers usually assign the quarterly bonuses!
To do the above effectively, a manager should know if a person is a good programmer—among other traits, of course. The question is, how do they do it? They don't even look at the code people write, they can't directly assess the quality of the components programmers develop... but their estimates of who is a good coder, and who is "not as good" are nevertheless correct in most cases!
What is the secret?
© Programmers or respective owner