|
|
|
|
|
by mbreese
1740 days ago
|
|
I know it’s not an ideal support mechanism, but I think this is one of the services HN provides to the community (informally). It can provide backdoor/informal channels through engineers and founders to some rather large companies. Especially when other avenues fail. But for the community, in this case, not only Stripe gets to learn about the issue, but we can all take something from this about automated systems and needs for manual overrides/reviews. This type of “case-study” can help many other companies avoid similar problems. But we also get some of the back story from Stripe about why their systems are designed this way. What challenges they face that made these engineering choices make sense. I’m sorry that this happened to the OP. But at least this channel of communication exists. And I think we can all benefit from it. |
|