Re:My boss decided to add a “person to blame” field to every...
by kls on Friday June 29, 2012 @11:58AM
(#4177270)
We actually had a tradition at one of the places I worked at, where someone along the way brought in a trophy and the title was changed to something along the lines of best bug write. Anytime a bug broke the system the trophy was passed to the person that broke the system. It was actually light hearted and effective. We would make a big deal of passing the trophy, but no one wanted that trophy. It was not punitive, but more of a joke, kind of a simple reminder that I don't want to be the guy with the trophy on his desk.
Re:My boss decided to add a “person to blame” field to every...
by reitzensteinm on Friday June 29, 2012 @11:49AM
(#4177207)
I completely agree with that - the boss in the story sounds like a lost cause. My post was more of a speaking in general kind of thing.
I was going to go off on a tangent about the importance of good management, but I haven't ever had a boss (self employed then startups), so by missing half the picture I didn't really feel qualified.
Re:My boss decided to add a “person to blame” field to every...
by gte910h on Friday June 29, 2012 @12:13PM
(#4177374)
If you tell me to blame someone every time there is an issue, and you don't let me find out why, I'm going to blame you. Because it's your fault as the boss of the department till you let us prove specifically otherwise. That's what responsibility is.
I have a feeling it's more like: <git annotate>; "Oh, it's Bob's fault."