[korla]

I think you vastly oversimplify how easy this fix is likely to be. For all we know this may mean touching code in multiple repos, each with hard-coded lists of which cards are supported for some case or another. At least that is what it would mean to change something like this where I am now.

[varjag]

Oh wow, editing a hard coded list. Does one need a chisel for that?

[jedberg]

That is not how things work in the real world. Sure, the fix itself might take 30 minutes. But then you have to validate it. And run a canary. And crosscheck your revenue numbers to make sure it didn't have an adverse affect elsewhere.

That's a lot of work for something that will probably mean very little extra revenue.

[varjag]

I assume they already have the quality assurance pipeline in place at Tinder and don't need to reinvent it from scratch for every bug report.

[jedberg]

Of course they do. But it still takes time, effort, and resources to run through the QA pipeline.

[varjag]

https://xkcd.com/277/

[IggleSniggle]

Depending on the amount of technical debt, it could very well be a number of hard coded lists in a number of projects that may be under multiple teams and which may or may not include first party code. It’s not that fixes like this should be hard, it’s that sometimes they are hard despite themselves, for organizational reasons.

Edit: just for clarity, I’d love to fix this bug myself. I also have a million other easy fixes that I’d like to do and I have a manager to help me prioritize them.