代码质量：如何衡量开发人员的绩效？ [英] Code Quality: how to measure developers performance?
问题描述
我在一家软件开发公司工作，我们大约有100位产品开发人员，其中1/3是质量检查人员。最近，管理人员希望有一种更好的方法来评估单个程序员的性能，因此建议是使用错误报告作为衡量标准。有关开发人员的错误报告越多，他的情况就越糟。这似乎是不明智的，原因有很多，例如我无法告诉的。它是一种主观的衡量方式，开发人员从事不同复杂程度的不同项目。此外，如果以质量检查来衡量它们生成的错误报告的数量，则会有很多关于错误报告有效性的讨论。
I work for a software development company and we have around 100 people working on a product, 1/3 of these people are QA. Lately management wants to have a better way to rate individual programmers performance so the suggestion was to use bug reports as a measurement. The more bug reports on a developer the worse he is. This seems ill-advised for more reasons than I can tell e.g. it is a subjective way of measuring, developers work on different projects of differing complexity. In addition if QA is measured for the number of bug reports they generate there will be a lot of discussions about the validity of bug reports.
有什么更好的方法
一个建议是不要使用质量检查人员的错误报告作为衡量标准，而应使用外部的错误报告（例如Beta测试人员），
One suggestion would be to not use bug reports from QA as a measure and instead use bug reports from outside, like beta testers then when such public bug reports are issued also let QA be measured by it.
编辑：＃1阅读了一些出色的回答后，我认为上述问题是普遍存在的描述的度量标准是，它是负面的报告错误-它不鼓励产生高质量的代码。
#1 After reading some of your excellent responses I was thinking that the general problem with the above described metric is that it is negative reporting bugs - it doesn't encourage producing good quality code.
编辑：＃2我认为问题在于这是两个世界。一侧上有一些非程序员，他们基本上将程序员视为工作者，他们希望度量标准是loc / minute。然后我们有了程序员，他们希望将自己视为艺术家或工匠，请不要打扰我，我是c-o-d-i-n-g ：)我认为衡量质量不能通过度量来完成，而不是适得其反。取而代之的是，一个人如何对错误做出反应，改变的意愿，创造力以及最重要的工作质量是很重要的，但大多数不一定可以衡量。
#2 I think the problem is that it is two worlds. There are the non-programmers on one side who treat programmers as workers basically, they want metrics loc/minute preferably. Then we have the Programmers, who want to see themselves as artists or craftsmen, "please don't disturb me I am c-o-d-i-n-g" :) I don't think measuring quality can be done by metrics not without being counterproductive. Instead things how a person reacts to bugs, willingness to change, creativity and above all quality of work are important and but mostly not necessarily measurable.
推荐答案
尝试通过错误报告来衡量程序员的性能是一个坏主意。但是，尝试使用其他任何指标来衡量性能。无论您做什么，人们都会弄清楚如何玩游戏，并在不给您真正想要的东西的情况下给您测量的东西。
Trying to measure programmers performance with bug reports is a bad idea. However, so is trying to measure performance with virtually any other metric. No matter what you do, people will figure out how to game it and give you what you're measuring without giving you what you really want.
从Joel的< a href = http://joelonsoftware.com/items/2006/08/09.html rel = noreferrer>其他文章：
罗伯特·奥斯汀（Robert Austin）在他的《衡量和管理组织绩效》一书中说，引入新的绩效指标时有两个阶段。刚开始，您实际上会得到想要的东西，因为没有人知道如何作弊。在第二阶段中，您实际上会变得更糟，因为每个人都想出最大限度地提高您要衡量的东西的技巧，甚至以破坏公司为代价。
Robert Austin, in his book Measuring and Managing Performance in Organizations, says there are two phases when you introduce new performance metrics. At first, you actually get what you wanted, because nobody has figured out how to cheat. In the second phase, you actually get something worse, as everyone figures out the trick to maximizing the thing that you’re measuring, even at the cost of ruining the company.
这篇关于代码质量：如何衡量开发人员的绩效？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
