News for hackers. Stuff that matters.
Re:How we use tennis rankings for fixing bugs by Sodman on Wednesday October 07, 2020 @12:43PM (#24710026)
The halving of points every week something doesn't get done sounds like a great way to motivate engineers to finish tasks on time, but in reality most of these tasks aren't slipping because people aren't motivated - it's because they're de-prioritized by whoever's in charge of product decisions, or because the scope is bigger than originally estimated. If a task slips by a week, now it's worth half points, and quarter points the week after that etc. The motivation to "get it over the finish line" is also going to slump exponentially for anyone optimizing for rewards points, isn't that what we're trying to avoid in the first place?
Re:How we use tennis rankings for fixing bugs by plorkyeran on Wednesday October 07, 2020 @02:58PM (#24711430)
Halving the points every week something doesn't get done is exactly what you'd want if your goal is to encourage developers to either fix things quickly or don't bother at all, and abandon anything that turns out to be bigger than expected.

It's very strange that the author is claiming that it'll encourage getting things done.