4 ms·
There's something wrong with this whole line of thinking. Perhaps its the measuring of productivity by loc, or pages of documentation written (shudder). Or ma
by bsaunder 17y ago
There's something wrong with this whole line of thinking. Perhaps its the measuring of productivity by loc, or pages of documentation written (shudder). Or maybe its the strong negative tone of the whole document.
Maybe it's me, but if a manager can't figure out the good and the bad performers in the group and figure out how to get the most of the resources available, then perhaps the most useful change would be at the management level.
Get to know your people. Look at their code, talk to them about ideas. Are they producing? Is there resentment among the group?
Please don't measure productivity by loc/day or worse yet pages of documentation. Short and sweet can be much more productive than overly verbose and redundant.
- lief79 17y agoFrom what I've heard and read, it tends to have more to do with the manager either not working closely with the individuals and/or not understanding what they are doing. This is especially common when it's a non-developer managing the group. The best measure of productivity is the amount of functionality added and the number of bugs produced. Secondary metrics would be the same two numbers for when someone else makes the changes. Of course, the real trick is in accurately gauging the difficulty of the tasks.
- tesseract 17y agohttp://www.folklore.org/StoryView.py?story=Negative_2000_Lines_Of_Code.txt http://www.folklore.org/StoryView.py?story=Negative_2000_Lin... ;)