$23,148,855,308,184,500

[growing_older]

Not that I am in any way making light of your loss. My condolences. But this recent rationalization:

When your Broke an only have your Credit left to feed the Family? You'd be amazed what you will do..Let alone Give what you can to your Wife who is dying..before she goes..

seems quite a bit different from your previous description. It doesn't seem like broke and trying to feed the family when you buy fur coats and trips. Or when you gloat about how you took advantage of the system.

When the Wife Got Cancer? We ran up all the CC's to the max and then some, we knew we were going to go into bankruptcy from the Medical Bills anyway..
Gave her just about everything she ever wanted from Clothes, Fur Coat to taking several Trips... After She Died, I filed banktruptcy and started over.. The CC debts totaled over $55k back in the Mid 80's...btwn 11 cards.. just paying the Interest on them along the way..and I sold alot of the stuff afterwards and had over $15k to start over with... ;-)

But then, I also think your neighbors who take advantage of store return policies are immoral and should be guilty of fraud. I resent what they've done to make most retailers restrict legitimate returns and raise prices for folks like me who respect both the spirit and the letter of the law.

 

[gindie]

For us programming geeks, an explanation in a story published at Slashdot IT Story | Software Glitch Leads To $23,148,855,308,184,500 Visa Charges

"Recently several Visa card holders were, um, overcharged for certain purchases, to the tune of $23,148,855,308,184,500.00 on a single chargehttp://www.cnn.com/2009/US/07/15/quadrillion.dollar.glitch/index.html. The company says it was due to a programming error, and that the problem has been corrected. What is interesting is that the amount charged actually reveals the type of programming error that caused the problem. 23,148,855,308,184,500.00 * 100 (I'm guessing this is how the number is actually stored) is 2314885530818450000. Convert 2314885530818450000 to hexadecimal, and you end up with 20 20 20 20 20 20 12 50. Most C/C++ programmers see the error now ... hex 20 is a space. So spaces were stuffed into a field where binary zero should have been."

 

[Gone4Good]

It would have been fun watching them trying to process my 231,488,553,081,845.00 cash back reward claim.

 

[nanannjen]

For us programming geeks, an explanation in a story published at Slashdot IT Story | Software Glitch Leads To $23,148,855,308,184,500 Visa Charges

"Recently several Visa card holders were, um, overcharged for certain purchases, to the tune of $23,148,855,308,184,500.00 on a single charge. The company says it was due to a programming error, and that the problem has been corrected. What is interesting is that the amount charged actually reveals the type of programming error that caused the problem. 23,148,855,308,184,500.00 * 100 (I'm guessing this is how the number is actually stored) is 2314885530818450000. Convert 2314885530818450000 to hexadecimal, and you end up with 20 20 20 20 20 20 12 50. Most C/C++ programmers see the error now ... hex 20 is a space. So spaces were stuffed into a field where binary zero should have been."

Oh, I'm so glad that you posted this - I was sure that I remembered that number from my old IBM mainframe days in the 80's - I worked for a bank and that number showed up on a report total - took us a while to figure it out! As soon as I saw the article, I suspected that same bug - but I hadn't seen confirmation. Thank you!