3 ms·
So a few days ago I added a "Person to Blame" field to our bug tracking system... I thought I'd share how the "Person to Blame" field works for our team. You a
by dmlorenzetti 14y ago
So a few days ago I added a "Person to Blame" field to our bug tracking system... I thought I'd share how the "Person to Blame" field works for our team.
You added the "Person to Blame" field a few days ago. Therefore you're describing how you think the field will work.
To be clear, I don't have a horse in this race. I'm sole dev on the things I make, so the bugs always point back to me. But I do notice that you're arguing from intention, rather than from experience. Whereas the arguments others have raised against this field are largely based on observations about what similar decisions have done to other teams.
I also have to wonder about your idea that blaming people is going to change anything (even if it is friendly and family-like). You described how you changed your process for pushing your software out the door. And you state that the new process allows more bugs to go out the door. That sounds to me like a real, measurable, problem, that exists somewhere besides the people performing the process. So how is calling out individuals going to fix whatever actual, underlying problem was introduced by the new process?