活跃农民
- 积分
- 542
- 大米
- 颗
- 鳄梨
- 个
- 水井
- 尺
- 蓝莓
- 颗
- 萝卜
- 根
- 小米
- 粒
- 学分
- 个
- 注册时间
- 2016-9-1
- 最后登录
- 1970-1-1
|
他们肯定escalate 的时候把事实扭曲了。直接director 那个slack thread补充点context:
.--
Director: "Please prioritize". Waral dи,
You: "The code change from X team was implemented without our knowledge and caused inconsistency in xxx IDs in our system. I see two options:
- let X team fix their code to meet their release deadline. It's unreasonable for someone to land breaking changes and force other teams to change. They are responsible solely for their change. There are more than one solutions to a problem; X team could also look into ways to make ID backwards compatible with downstream.
- we give them a hand and implement a change on our side. With such a short notice, it is nontrivial for our team to come up with a well rounded solution to make sure things don't break on our side, or cause even more cascaded changes. If we agree this is the way forward, we need to follow our own timeline for this fix. Bear in mind each team has their own priorities as well."
补充内容 (2022-02-21 05:23 +08:00):
在同一个thread怼一下tpm
"@tpm From our discussions, We didn't feel any appreciation if we were to fix your breaking change. This is a favor not an obligation and people usually ask for a favor not escalate one. The fact that your team is making a breaking change without noticing other teams means there is a larger problem in your process. You will likely see a smoother feature roll out if you plan ahead next time. ..
补充内容 (2022-02-21 05:43 +08:00):
基本上就是让大家都知道这个锅是TPM来背,如果他们feature launch 晚了是这个TPM没交流好。现在没啥实质上的东西可以搞他,但你其实已经掌握了他们的命脉;你可以去fix 但要以你的节奏来。你能托多久他就难受多久。
你可以找各样借口:
- 生病休假(1周)
- 组内有更high priority 的火要救(1周)
- 你可以放大难度, performance 影响要调查(1周), patch 需要时间测试(1周), patch 需要人review + address comments (1周) |
|