3 ms·
This is the pat answer Amazon gives to defend this absurd practice, but it breaks down really easily. >If your code breaks something, you should fix that code.
by dimmke 4y ago
This is the pat answer Amazon gives to defend this absurd practice, but it breaks down really easily.
>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.
- nevon 4y agoThat's still your code ("your" meaning the team that owns the product). Who else would own it? The person that left 3 years ago?
- Firmwarrior 4y agoThe problem is that he has a big pile of half-working spaghetti code that he never has time to touch except when it malfunctions in the middle of the night 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
- dimmke 4y agoAlso usually it’s in Java in an internal framework based off Springboot and I’m a front-end developer with no experience writing backend services. Totally normal. Not crazy at all. Take ownership.
- Firmwarrior 4y agoYou should join Amazon and do that, and you can come back here and apologize in a couple of years when you get pipped for wasting too much time on legacy code