11–20 of 68 posts
What’s that boast again, “move fast and break things” …
Just the style here throws me.
Are all these articles this "lightweight" and short on details and sound like a made up coding morality tale? Just the style here throws me.
It turned out very profitable for the company though. Stonewalling customers and refusing charge backs is too easy. Not picking up the phone is a good business strategy.
Reminds me of a similar bug in a payment processing system the company I worked for used. Long story short, overflow in Java numerical types (counting milliseconds for durations in weeks...) caused the system to go haywire and charge customers 1000x the normal amount... It turned out very profitable for the company though. Stonewalling customers and refusing charge backs is too easy. Not picking up the phone is a goo…
Reminds me of a similar bug in a payment processing system the company I worked for used. Long story short, overflow in Java numerical types (counting milliseconds for durations in weeks...) caused the system to go haywire and charge customers 1000x the normal amount... It turned out very profitable for the company though. Stonewalling customers and refusing charge backs is too easy. Not picking up the phone is a goo…
That doesn't sound right...? Credit/debit card chargebacks are handled by the bank. If the merchant doesn't pick up the phone, the bank will take the money from the merchant and return it to the customer.
https://www.usatoday.com/money/blueprint/credit-cards/credit...
Were you using a different payment system with fewer consumer protections than credit/debit cards?
This read to me as if someone asked a LLM to create a facebook urban legend about a bad programmer and prompted it with a couple bullet points. If it contained the words “you’ll never believe what happened next…” they would be completely at-home.