This idea of "everyone pitches in" works only if everything else is going well too. I'm happy to pitch in to help fix something, but if the rest of the gang steadfastly refuses to do anything to make their stuff better in the future - in other words, if they keep writing piss poor code knowing that I'll be the one to "pitch in" when it crashes - then thanks but no thanks.
I'm truly grateful when others step in to fix something I broke, but I then need to learn from them so I don't do it again. I was working with a team recently and kept breaking some of their git process with my check-ins. Code worked, but I was doing something that went against their flow. Took me a while to sort it out, and I felt bad because it was costing one of the other guys time. I finally grokked what he was asking for, and I've caused much less downtime.
His attitude initially was "hey, that's no sweat - I can fix this up". That started wearing thin by the 4th mistake, and I could tell. I felt bad, but eventually got to the point where I'm not slowing them down anymore.
I've been on teams where other people continually write crap code - never bothering to even check if it works - then I have the bad attitude for not fixing it: not being a "team player", etc. That's gotta work both ways.
So, yeah, "not my job" isn't a great attitude. You do have to ask tho, when you see that attitude, how much of it is endemic to that person, and how much of it is caused by something more systemic in the organization?
I'm truly grateful when others step in to fix something I broke, but I then need to learn from them so I don't do it again. I was working with a team recently and kept breaking some of their git process with my check-ins. Code worked, but I was doing something that went against their flow. Took me a while to sort it out, and I felt bad because it was costing one of the other guys time. I finally grokked what he was asking for, and I've caused much less downtime.
His attitude initially was "hey, that's no sweat - I can fix this up". That started wearing thin by the 4th mistake, and I could tell. I felt bad, but eventually got to the point where I'm not slowing them down anymore.
I've been on teams where other people continually write crap code - never bothering to even check if it works - then I have the bad attitude for not fixing it: not being a "team player", etc. That's gotta work both ways.
So, yeah, "not my job" isn't a great attitude. You do have to ask tho, when you see that attitude, how much of it is endemic to that person, and how much of it is caused by something more systemic in the organization?