Hacker News Reader

Comment by CharlesW | Hacker News Reader

Reading the post is how I learned the developer didn't file Technical Support Incidents (TSIs).

Almost every time, developer technical support will look at the internal bug and if there is no known workaround will say “sorry that’s our bug and engineering is investigating, we don’t have anything to tell you, please keep an eye on the feedback and we will update you if anything changes - in the meantime here’s your TSI refunded”.

Ooof. That’s a terrible experience, thank you for sharing.

In that process though, you’ve had someone at Apple verify that your issue is legitimate, and that issue has probably shown up in a place they care about (DTS metrics)

Two things that simply filing a feedback issue doesn’t seem to reliably do.

I’m suspect a concerted effort to get developers using their TSIs for bug reporting would backfire (stop refunding them? remove the program?), but I think it’s an interesting idea given how cheap the TSIs are for developers.

Sure and I don’t mean to minimise the value/effort - I’m sure the “look at” may involve actually investigating the issue themselves by looking at the implementation, speaking with the responsible engineers, etc. I am also sure it is a hard problem to solve - while Apple is massive and well resourced these days their developer community is also humongous and I am sure there is a tremendous amount of noise. But my point is merely - TSIs are not a panacea

Reply on news.ycombinator.com