Timeline for I am making 4-5x more story points than average, but producing bugs at half the rate. Graphs say it's 2x more bugs, how to deal with that?
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2014 at 11:22 | audit | First posts | |||
| May 22, 2014 at 11:24 | |||||
| May 21, 2014 at 14:00 | comment | added | Huperniketes | @GlenH7- Again, programmers have trouble with clear reasoning. A line of buggy code is several times more expensive than one which is bug-free. Managers grok this. Look at GM's defective ignition fiasco, and grok this. You cannot reasonably spew lines of code thinking testers and maintainers will clean it up afterwards. Just quit spewing out junk from the get-go. | |
| May 19, 2014 at 19:21 | comment | added | Dawood ibn Kareem | No. It's not about a manager looking at raw number of bugs, or any other metric. It's about a manager who wants his employee to perform better, and an employee who thinks he/she is justified in not complying. | |
| May 18, 2014 at 13:30 | history | edited | user53019 | CC BY-SA 3.0 |
Addressed the comments getting lost in the trees and missing the forest.
|
| May 18, 2014 at 13:06 | comment | added | user53019 | @Huperniketes - you're missing the point. The core of this question is about a manager looking at raw numbers of bugs versus the rate of generation. Nothing within the comment you're complaining about encourages poor craftsmanship. It merely reflects that a programmer with higher productivity will more quickly finish a comparable task than someone with lower productivity. | |
| May 18, 2014 at 4:40 | comment | added | Huperniketes | This answer, and the community's support of it, is a great example of the muddled thinking rampant in our industry, that software is terribly written because programmers have such difficulty with logic and clear reasoning. "If anything, higher productivity means you'll have more time at the end of the project to hunt those bugs down or the developer will be faster in finding the bugs they created." That's insane. "Let's first add all the features, and we'll debug afterwards. Then we'll show how fast we code, and how fast we debug, etc. It's much easier fixing bugs when they're all present!" | |
| May 17, 2014 at 12:53 | vote | accept | Telastyn | ||
| May 17, 2014 at 2:52 | audit | First posts | |||
| May 17, 2014 at 2:52 | |||||
| S May 16, 2014 at 16:27 | history | suggested | user86771 | CC BY-SA 3.0 |
Pretty sure you mean that; minor edit at the end because 6 characters
|
| May 16, 2014 at 16:10 | review | Suggested edits | |||
| S May 16, 2014 at 16:27 | |||||
| May 15, 2014 at 23:06 | comment | added | occulus | "If anything, higher productivity means you'll have more time at the end of the project to hunt those bugs down or the developer will be faster in finding the bugs they created." - I think this is spurious and needs more careful anaylsis. Put it this way: if he spent more time on each feature, yeah, he'd have less time to squash bugs. But there would also be less bugs to squash. | |
| May 15, 2014 at 22:08 | comment | added | Pete Kirkham | "Your best developers should be creating more bugs because they're writing more code." no, they should be either preventing bugs or finishing more features. Often that means they write less code, or even remove swathes of code. ( you probably know that, just didn't quite write it that way ) Certainly in some industries I've worked in, (e.g. aerospace and nuclear ) the only code which counts is the code which is proven to have zero defects. Anything else is noise. | |
| May 15, 2014 at 14:09 | comment | added | Bart van Ingen Schenau | Bugs/K lines or bugs/storypoint would be a fair rate. I would run as fast as I can if the boss wants to use bugs/hour as a rate. | |
| May 15, 2014 at 14:00 | comment | added | hlovdal | Great programmes might actually produce more errors than the average programmer - because great programmes tend to work on harder problems. | |
| May 15, 2014 at 13:43 | history | edited | user53019 | CC BY-SA 3.0 |
added 1115 characters in body
|
| May 15, 2014 at 13:39 | comment | added | Neil | "Measuring programming progress by lines of code is like measuring aircraft building progress by weight." -Bill Gates | |
| May 15, 2014 at 13:37 | history | answered | user53019 | CC BY-SA 3.0 |