Skip to main content
39 events
when toggle format what by license comment
Aug 26, 2013 at 7:12 history closed gnat
CommunityBot
mattnz
Kilian Foth
Duplicate of 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?
Aug 25, 2013 at 0:29 review Close votes
Aug 26, 2013 at 7:12
Sep 20, 2011 at 8:57 comment added Newtopian what about bugs created because the requirements were not gathered correctly, or because the architect made a bad call, or because that was a requested change made through ad-hoc channels (verbally by the designer or architect or customer for example). will the stick apply to them also or just to developers ? What if I (as a developer) identifier this as a potential problem but got overridden by higher power and it finally did turn out as a bug, should I get the rap ?
Sep 20, 2011 at 8:48 comment added h0b0 Check out what Joel says about how such metrics would be sooner or later circumvented: joelonsoftware.com/items/2006/08/09.html
S Sep 19, 2011 at 18:52 answer added Vector timeline score: 0
S Sep 19, 2011 at 18:52 history made wiki Post Made Community Wiki by Vector
Aug 13, 2011 at 13:04 answer added David Schwartz timeline score: 0
Aug 11, 2011 at 16:02 answer added Sonic Death Monkey timeline score: 0
Aug 11, 2011 at 14:33 comment added ccozad Didn't have a long enough response to contend with the others, but the phrase "Fix the problem. not the blame" discussed in The Pragmatic Programmer comes to mind.
Aug 11, 2011 at 12:39 answer added jwernerny timeline score: 3
Aug 11, 2011 at 12:02 answer added Nemanja Trifunovic timeline score: 5
S Aug 11, 2011 at 10:03 history suggested Skeith CC BY-SA 3.0
spelling & grammar
Aug 11, 2011 at 9:37 review Suggested edits
S Aug 11, 2011 at 10:03
Aug 11, 2011 at 9:31 answer added dagnelies timeline score: 1
Aug 11, 2011 at 9:07 history edited WinW
edited tags
Aug 11, 2011 at 8:47 answer added Bevan timeline score: 1
Aug 11, 2011 at 5:55 answer added WinW timeline score: 17
Aug 11, 2011 at 4:07 vote accept zengr
Aug 11, 2011 at 2:52 answer added Joel Coehoorn timeline score: 8
Aug 11, 2011 at 2:04 answer added Caleb timeline score: 18
Aug 11, 2011 at 1:45 answer added James Anderson timeline score: 3
Aug 11, 2011 at 0:40 history tweeted twitter.com/#!/StackProgrammer/status/101452782590103552
Aug 11, 2011 at 0:31 answer added maple_shaft timeline score: 8
Aug 10, 2011 at 23:58 answer added user29981 timeline score: 4
Aug 10, 2011 at 23:50 answer added JohnFx timeline score: 145
Aug 10, 2011 at 23:43 answer added Tangurena timeline score: 48
Aug 10, 2011 at 23:29 comment added Thomas Owens @JohnFx The original question was questionable. In fact, it was closed at one point because it was too open ended and invited long-standing discussion. Check out the post history to see what it was like before/after. I believe the downvotes are left over from the after.
Aug 10, 2011 at 23:28 comment added Kevin if there's 3 bugs every time you make a check-in maybe there should be some penalty. If there's 3 bugs every month and qa finds them anyway who cares?
Aug 10, 2011 at 23:26 comment added JohnFx The down votes seem a bit harsh. We are voting on the validity of the question not the concept of penalizing developers.
Aug 10, 2011 at 23:05 history reopened zengr
Thomas Owens
Adam Lear
Aug 10, 2011 at 22:52 history edited Thomas Owens CC BY-SA 3.0
added 49 characters in body; edited tags; edited title
Aug 10, 2011 at 22:46 history edited zengr CC BY-SA 3.0
added 385 characters in body
Aug 10, 2011 at 22:32 comment added FrustratedWithFormsDesigner @Mchl: I suppose that's the only organization where such a policy would make sense.
Aug 10, 2011 at 22:18 history closed Adam Lear not a real question
Aug 10, 2011 at 22:14 comment added Mchl Only if developers are paid per LOC produced daily.
Aug 10, 2011 at 22:12 history reopened Adam Lear
Aug 10, 2011 at 22:11 history closed Adam Lear not constructive
Aug 10, 2011 at 22:11 answer added JB King timeline score: 5
Aug 10, 2011 at 22:07 history asked zengr CC BY-SA 3.0