Re:Failing (and winning) at planning software projects
by maaarghk on Wednesday June 17, 2020 @10:41AM
(#23551990)
https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s...
[ Parent
| on HN ]
Re:Failing (and winning) at planning software projects
by commandlinefan on Wednesday June 17, 2020 @04:31PM
(#23556379)
Reminds me of a recent Dilbert comic/quote: "Our boss can't judge the quality of our work, but he knows when it's late".
Re:Failing (and winning) at planning software projects
by marcoow on Wednesday June 17, 2020 @10:44AM
(#23552031)
Sure, you should have bugs documented somewhere but I'm not sure a bug that hasn't been fixed for x months needs to be there since it's a bug the team obviously decided not to care about.
Re:Failing (and winning) at planning software projects
by watwut on Wednesday June 17, 2020 @11:26AM
(#23552548)
I personally fixed bugs that have been opened for longer then that, so nope, they can get fixed. Plus, it prevents people from opening them again and again and again and again as they all notice the same thing.
Re:Failing (and winning) at planning software projects
by cpeterso on Wednesday June 17, 2020 @11:42AM
(#23552724)
I've fixed a couple Firefox bugs that were filed in Bugzilla 10-15 years ago. :)
At least one fix, however, upset some people who come to like the "incorrect" behavior over those 10-15 years. (In one case, I changed the filename of saved web pages from "index.html" to HTML <title> .html to match Chrome and IE behavior.)
This xkcd comic is relevant: https://xkcd.com/1172/