If your code breaks something, you should fix that code. Who else should?
If your system/product/service is down because you have a dependency on something that broke -- well it's up to that team to fix their code.
If your system/product/service is down because you have a dependency on something that broke -- well it's up to that team to fix their code.
>If your code breaks something, you should fix that code. Who else should?
What if it wasn't my code, but code written by someone 3 years ago who quit because most people only work at the company for 2 years? And it's in a part of the codebase I've never touched. That's a much more likely scenario.
The problem behind that is that Amazon is a completely dysfunctional corporate hellscape. Like TFA said, you just don't have time or resources to actually fix things
Totally normal. Not crazy at all. Take ownership.