Timeline for My boss decided to add a "person to blame" field to every bug report. How can I convince him that it's a bad idea?
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 28 at 17:33 | comment | added | Questor | @JorisTimmermans Except they don't have testers anymore because the fired their QA team. | |
Oct 25, 2020 at 17:57 | comment | added | gnasher729 | Malachi. I worked with a guy once, and everything he touched broke. Whether it was code that he hadn’t written or office furniture, he touched it, it broke. I would not have hesitated to add him as "root cause" of any bug he reported:-) | |
Jun 21, 2016 at 3:06 | history | wiki removed | user28988 | ||
Sep 28, 2012 at 18:46 | comment | added | Malachi |
The Person Reporting the Bug will not likely be the person that is the root cause I mean think about trying to find a an error in your own code after 36 hours of writing code this week?
|
|
Jun 29, 2012 at 13:50 | comment | added | Joris Timmermans | From experience, this is not a "probable" result, it's 100% absolutely certain that this will happen, because developers are smart people. What you will also see is a massive increase time spent arguing violently with testers that their "bugs" aren't bugs. | |
Jun 29, 2012 at 12:35 | comment | added | Matt Wilko | The boss is probably on performance related pay and one key performance indicator is the number of bugs reported. Hopefully he/she will share out his bonus to the development team at the end of the year. | |
Jun 29, 2012 at 1:04 | history | made wiki | Post Made Community Wiki by hasanyasin | ||
Jun 28, 2012 at 21:27 | comment | added | nicodemus13 | Well, the boss will be happy! There'll be fewer bug reports, and therefore, the quality must have gone up. | |
Jun 28, 2012 at 20:32 | history | answered | Laurent Parenteau | CC BY-SA 3.0 |