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.
i mean the register is kinda more of a tabloid than anything, it's real-ish news but with a loose and snarky editorial style, so... it's pretty on-brand.
Coder wrote a bug so bad security guards wanted a word when he arrived at work
41–50 of 68 posts
Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work
#42Earlier quoted context omitted.
This is not a true story because as a merchant you cannot "refuse chargebacks". In fact too many chargebacks will result in a loss of your merchant account. You should really stop making things up.
Sorry Sherlock, I meant charge back as in "refunds" not credit card disputes. Also, merry Christmas.
Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work
#43Earlier quoted context omitted.
Not unheard of, unfortunately. Funny enough, in a fintech I worked for, developers and QAs actually used their own personal credit cards and bank accounts for testing. Interestingly, they also needed to test ApplePay, but the laptops didn't allow for adding their personal iCloud accounts. So someone in the development team got the "admin" password and distributed among devs and QA team, and they all had unprotected l…
I wonder if NOT providing a separate, exclusive account/card/sim etc to a developer is a common trope in fintech. I avoided linking my personal things like hell, and they avoided giving me a damn immutable plastic that would work/get paid for more than a few days. So much friction just because something stopped working or had to get back into oven and they had no replacement at hand. I even had to maintain a separate…
Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work
#44Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work
#45In the end, it turned out OK. The joint burned down, and Milton ended up on a beach, sans Swingline.
Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work
#46I worked for a large retailer on their iPhone app and our test environments were terribly slow so we tended to do most of our development against production. This retailer is pretty old and had issued their own credit cards that didn't have any sort of checksum validation. This made making test orders easy because any sequence of numbers for that credit card type would let the "checkout" call succeed, and then the or…
Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work
#47Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work
#48I worked for a large retailer on their iPhone app and our test environments were terribly slow so we tended to do most of our development against production. This retailer is pretty old and had issued their own credit cards that didn't have any sort of checksum validation. This made making test orders easy because any sequence of numbers for that credit card type would let the "checkout" call succeed, and then the or…
One day, we got a big box of makeup at the office - turns out their warehouse had gotten so fast that in the time it took us to cancel the order they had already picked & shipped it.
After that we put "TEST DO NOT SHIP TEST DO NOT SHIP" as the shipping name and "123 Fake St" as the address to try and avert this scenario, which seemed to work until we could modify the system to hide those orders from the warehouse entirely.
Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work
#49There was a tiny bit of logic in there if I remember correctly, relating to when and whom to show the ad to.
I implemented it, tested in dev, assigned it to QA, QA approved it and rolled it out that afternoon.
The next morning when I showed up to work one of the other team leads walked straight up to me as I entered the campus, laughing hysterically.
Turned out that in production it behaved differently. The ad appeared, correctly. Then doubled every couple of seconds,1 ad, 2 ads, 4 ads and so on, until the client browser exploded into flames.
As luck would have it there was zero consequence, only chuckles all over the place. It was something to do with order of inclusion of a mad number of js libraries which differed in production and went unnoticed. The End.