> Should, but don't, is not doing their job. Most engineers don't have the luxury of using this defense their day to day job. Yeah, I should be doing testing, but I don't know. I should be writing clean code, but I don't know. I should be communicating with my colleagues, but I don't know.
This is needlessly antagonistic. All teams have gaps, but effective teams help each other out. For instance, a good manager will give you air cover when things are underestimated or unforeseen difficulties arrive. Similarly, good engineers will point out risks and potential problems even if it is not directly in their execution path.
The most toxic teams are ones where everyone keeps their head down and looks for every opportunity to say "not my job" whenever any larger or unusual challenges are identified. Based on your comment it seems like you think that ICs can't get away with this, but managers can, and I assure you that neither is true.
This is needlessly antagonistic. All teams have gaps, but effective teams help each other out. For instance, a good manager will give you air cover when things are underestimated or unforeseen difficulties arrive. Similarly, good engineers will point out risks and potential problems even if it is not directly in their execution path.
The most toxic teams are ones where everyone keeps their head down and looks for every opportunity to say "not my job" whenever any larger or unusual challenges are identified. Based on your comment it seems like you think that ICs can't get away with this, but managers can, and I assure you that neither is true.