4 ms·
For a PayPal employee to post here and say he made a team aware and they are working on this it's utterly laughable. There was a post here on hn over two years
by shabbaa 11y ago
For a PayPal employee to post here and say he made a team aware and they are working on this it's utterly laughable.
There was a post here on hn over two years ago for the same issue which was top post and generated a lot of news.
https://news.ycombinator.com/item?id=6526481 https://news.ycombinator.com/item?id=6526481
It is obviously very well known to them for years but they continue to do it
- rtpg 11y agoObviously well known? Guy at PayPal sees post, tells a technical person about it, said person forgets about it. Suddenly PayPal doesn't know about it anymore. Or a person wants to work on fixing this but a manager says no, because there are other priorities. Or a person starts working on this, quits, and it gets lost among the things they were working on. It's so easy for things to get lost in a company, even with all the bug trackers in the world.
- r00fus 11y agoIsn't this what support case systems and bug tracking software was meant to do - to track non-closed issues?
- DrScump 11y agoThat assumes that the manager doesn't insist that bugs of age get closed simply because long-open bugs make for ugly metrics.
- rtpg 11y agoyeah, I agree, but I think a lot of us work in similar situations, where bug tracking exists, but there's such inundation of bugs that we can lose track of some. I guess I have sympathy for the PayPal team in this case. They're working on an extremely large product, with a huge user-base. I would imagine it would be very easy for bugs like this to fall through the cracks even with a "process" in place