3 ms·

Frankly if this actually happened, I would do neither. Just tell my IC "I'm not sure why your work was invalidated. Let me look into it for you." and then addre

by warent 4y ago

Frankly if this actually happened, I would do neither. Just tell my IC "I'm not sure why your work was invalidated. Let me look into it for you." and then address this as a grievous issue on behalf of my IC with the leadership. If leadership doesn't fix the problem then just resign in protest. EDIT: It's now occurring to me that there's probably different schools of thought here. Yes, I've resigned in protest on behalf of my workers before. If my team is getting fucked, then I've either failed my team, or my purpose is meaningless. Either way, get me out.

skipidarink 4y ago
> Just tell my IC "I'm not sure why your work was invalidated. Let me look into it for you." And so you take your first step down the path.. "I'm not sure" is a lie here.
- deleted 4y ago
  [deleted]
- warent 4y ago
  Why do post mortems happen for production issues, when you could just open up "git blame?" Are you lying to the team when you say, "we're not sure how this happened" rather than just quoting the git blame? Well, no. The problem is much more complicated than a buggy commit. It's a wider problem with the system. So you say "we don't know, we have to look more into it" and do a post mortem because that is the honest truth. The same principle applies here. So-and-so highly respected person committed a real-life communication bug that got merged into this IC's production career. But the problem is much more complicated than that. You don't know what the actual problem is until you address it with the leadership team.
  - skipidarink 4y ago
    I hear you on all of that, I'm just saying that leadership gets complicated. Sometimes the lie is better for all involved, especially the IC. You recognized this with your first instinct on how to communicate it. As far as the rewards for poorly-motivated actions, we've always got the long term.

by warent 4y ago

skipidarink 4y ago

> Just tell my IC "I'm not sure why your work was invalidated. Let me look into it for you." And so you take your first step down the path.. "I'm not sure" is a lie here.

deleted 4y ago
[deleted]
warent 4y ago
Why do post mortems happen for production issues, when you could just open up "git blame?" Are you lying to the team when you say, "we're not sure how this happened" rather than just quoting the git blame? Well, no. The problem is much more complicated than a buggy commit. It's a wider problem with the system. So you say "we don't know, we have to look more into it" and do a post mortem because that is the honest truth. The same principle applies here. So-and-so highly respected person committed a real-life communication bug that got merged into this IC's production career. But the problem is much more complicated than that. You don't know what the actual problem is until you address it with the leadership team.
- skipidarink 4y ago
  I hear you on all of that, I'm just saying that leadership gets complicated. Sometimes the lie is better for all involved, especially the IC. You recognized this with your first instinct on how to communicate it. As far as the rewards for poorly-motivated actions, we've always got the long term.