> In order to measure software engineering productivity, we need...
I think it is well established at this point that turning dev work into "metrics" is a bad idea. From LOC being a bad measure with bad incentives, to the example of those senior folks who deliver little code but solve all the problems behind the scenes, there simply isn't a fair metric for this kind of work. Trying to build a baseline of what to measure is a shoddy foundation for good engineering management.
People on dev teams know who is a solid teammate and who is not. If you need that type of answer, don't measure, just communicate.
Also, from the HN guidelines: "Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity." It is fairly evident when a new account doesn't comment on anything and just posts content related to their own product. Please engage with HN on a deeper level if you want us to engage with you.
codingdave•8mo ago
I think it is well established at this point that turning dev work into "metrics" is a bad idea. From LOC being a bad measure with bad incentives, to the example of those senior folks who deliver little code but solve all the problems behind the scenes, there simply isn't a fair metric for this kind of work. Trying to build a baseline of what to measure is a shoddy foundation for good engineering management.
People on dev teams know who is a solid teammate and who is not. If you need that type of answer, don't measure, just communicate.
Also, from the HN guidelines: "Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity." It is fairly evident when a new account doesn't comment on anything and just posts content related to their own product. Please engage with HN on a deeper level if you want us to engage with you.