Live data from Hacker News

Coder wrote a bug so bad security guards wanted a word when he arrived at work

theregister.com

61–68 of 68 posts

Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work

#61
post #2

This reads a bit like an article from "the daily wtf", I used to frequent that one often [0]. [0] https://thedailywtf.com/

I still have their mug! (Which my child consistently gives me shit for. "Dad, why we we have a cup with the F-word on it!?")

Didn't they rebrand, briefly, as "Worse Than Failure", before going back to the real meaning?

Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work

#62
post #53

Earlier quoted context omitted.

I recommend to edit your post with an "update" so others don't have to dig to find this clarifying comment

HN locks out edits after a little while.

It does. I believe that window is greater than 4 hours. Pity in the meantime since anyone that does not drill in will be mislead

Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work

#63
post #57

A couple of years ago, I lived in an apartment and made a doorbell repurposed from an Amazon Dash button. Basically I have a daemon that sends a message each time a button press is detected to my homebrew mqtt server. Then I have a bash script that runs on the raspberry pi board that has a speaker installed, something of this sort to play the doorbell chime: while [ true ]; do mosquitto_sub --exit-after-first-message…

SSHing to your doorbell to make it stop bothering your neighbor would be an awesome move

I used all my brain cells to make a bash script my doorbell, I did not have brain cells left to envision ever needing ssh on it.

Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work

#64
post #2

This reads a bit like an article from "the daily wtf", I used to frequent that one often [0]. [0] https://thedailywtf.com/

I still have their mug! (Which my child consistently gives me shit for. "Dad, why we we have a cup with the F-word on it!?")

Welcome The Future!

Yes, son, the Future is the new F-word. And you'll be living in it. You're welcome.

Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work

#65
post #53

Earlier quoted context omitted.

HN locks out edits after a little while.

It does. I believe that window is greater than 4 hours. Pity in the meantime since anyone that does not drill in will be mislead

the window is exactly two hours

Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work

#66
post #46

I 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…

They literally didn't have a Lunh check digit? Like, 1960s math? My gobs are smacked.

The theory was that the numbers were issued sequentially and they only kept them around because there was some "prestige" around having a low number. Not sure if that's true, but they did end up changing to a regular Visa card not long after. These cards only worked at that retailer and were originally issued long before the Internet.

Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work

#67
post #11

What’s that boast again, “move fast and break things” …

Breaking things isn't ideal, but it's not the worst. What's truly problematic is when everything appears to be functioning perfectly, while underlying issues go unnoticed—exactly the situation in this story.

Moving fast by releasing unreviewed code into critical production paths can lead to breaking things, as this story illustrated.

It’s the same cavalier attitude taken by startups that treat user data and privacy as something to worry about later, someday.

Re: Coder wrote a bug so bad security guards wanted a word when he arrived at work

#68
post #58

Earlier quoted context omitted.

I worked on a large makeup website for a while, and it was common for us to place test orders and subsequently cancel them. The dev doing it usually put their name and the office address as the shipping address. 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 D…

One day, we got a big box of makeup at the office now that's a true end-to-end test.

Oh my, thats funny.

?id=48391&test=lol

Post reply on HN