Live data from Hacker News

Count to ten when a plane goes down

johncbeck.tumblr.com

201–210 of 284 posts

Re: Count to ten when a plane goes down

#201
post #113

How about when Russia returned the data recorders after years of refusing to South Korea - made a press spectacle of it - and then South Korea discovered the recorders were empty and missing the data tapes when the press was gone. Or the US navy crew who received medals after shooting down the Iranian airline. Once there is loss of life, it is 100% politics afterwards with little to no practicality, just look at all…

> We simply do not value life, it is politics first.

We value life just fine, but the sociopaths in charge all over the world don't.

Re: Count to ten when a plane goes down

#202

Earlier quoted context omitted.

> Not really, a lot of novice unix users are of the habit of removing files with -rf switch. I cringe everytime I see it. Every few days I remind myself of this.... then I have to delete another directory with a git repository in it, and end up add the -f in again

I run into this all the time, too. Now my -rf usage is almost always wrapped by this: rmgit() { git status read -p "Are you sure? " -n 1 -r echo if [[ $REPLY =~ ^[Yy]$ ]] then rm .git -rf fi }

I think this would be a bit better for interactive cases. Note: written just now, I haven't actually felt the need for this safeguard... yet.

    rmrf()
    {
        (echo "The following files are going to be deleted!!!"
         for FILE in "$@"; do
             echo ">>"
         done) | less
        read -p "Are you sure? " -n 1 -r
        echo
        if [[ $REPLY =~ ^[Yy]$ ]]
        then
            rm -rf "$@"
        fi
    }

Re: Count to ten when a plane goes down

#204
post #45

Earlier quoted context omitted.

That button needs a safeguard even if it's not an international incident. Even if only one person would lose a few hours' work from an all-nighter, work for something that's not so important, it's still someone's work. And given that it's right next to a 'single terminal reset' key, it should be immediately obvious to anyone who's ever used a keyboard - mistakes can and do happen, even when you're fluent.

And yet, to this day, Firefox has both Ctrl-Q (close all Firefox windows without prompting) and its neighbor Ctrl-W (close current tab) and refuses to change that or provide remappable keyboard shortcuts. One of the biggest UI failures I'm aware of in 2014. https://bugzilla.mozilla.org/show_bug.cgi?id=52821

Ctrl-Q exits on Thunderbird too. Since in MS Outlook that combination marks a mail as read, for keyboard-heavy users switching between the two, it is no fun.

Re: Count to ten when a plane goes down

#205
> On this day, I highlighted her workstation and hit the F6 key to reset. But my screen went temporarily black and then seemed to be starting again. I realized that I had mistakenly hit F7 and reset all the workstations in the embassy.

Ugh.

Those with automation capabilities: keep this lesson in mind, because it will happen to you in production one day. 'dsh -a reboot' is incredibly easy to type and can have disastrous effects. Creating abstraction layers around common admin tasks can help catch simple mistakes and give prompts before dangerous behavior.

Re: Count to ten when a plane goes down

#206

The author states they felt it was appropriate when they were fired. In what world would it be appropriate to get fired for a single, simple, incredibly easy to make mistake? Doubly insane when there were exactly zero safeguards in place to prevent the mistake from being made.

When so many people higher up are given incomplete information or even downright embarrassed on the world stage because of one simple mistake, I feel it is appropriate. It is still, however, doubly insane that one person's stray keystroke can do all of that.

Re: Count to ten when a plane goes down

#207
Firstly, firing the intern doesn't make sense - it was a mistake waiting to happen and he just happened to do it at the wrong time.

Secondly, the punishment meted out should be:

1. Proportional to the degree of carelessness (in this case not that much since he accidentally hit a wrong key adjacent to the right one, didn't mow down anybody while driving drunk)

2. Inversely proportional to the likelihood of the error (in this case the likelihood was very high since the reset key was a. uncovered/single-press b. right next to single reset key).

3. Proportional to intention (this was a completely unintentional error)

If you say, that the punishment should also be dependent on the degree of damage, I would say that the responsibility of managing the risk of such damage wasn't his but of the person responsible for implementing such a high risk design. If such a person is not around, find the person who approved such a design. Government departments are usually very good with paper trail.

Re: Count to ten when a plane goes down

#208
post #200

Earlier quoted context omitted.

And yet, to this day, Firefox has both Ctrl-Q (close all Firefox windows without prompting) and its neighbor Ctrl-W (close current tab) and refuses to change that or provide remappable keyboard shortcuts. One of the biggest UI failures I'm aware of in 2014. https://bugzilla.mozilla.org/show_bug.cgi?id=52821

This in combination with "Restore all tabs on startup" not being the default is a disaster. The first thing I do on a new Firefox installation is enable "Restore all tabs on startup".

Even without that flag enabled, you can restore all tabs when closing/reopening Firefox. History > Restore Closed tabs.

Re: Count to ten when a plane goes down

#209
post #200

Earlier quoted context omitted.

This in combination with "Restore all tabs on startup" not being the default is a disaster. The first thing I do on a new Firefox installation is enable "Restore all tabs on startup".

Even without that flag enabled, you can restore all tabs when closing/reopening Firefox. History > Restore Closed tabs.

Thanks, good to know.

Re: Count to ten when a plane goes down

#210
post #79

Earlier quoted context omitted.

Ten years prior to that, Apple had a similar bug in one of its installer scripts on OS X. I have a hard time finding much about it online now, because it happened at a time when OS X and the Internet were a lot less popular than today, but what I recall is that an unexpectedly customized installation directory (say with spaces or one level closer to "/" than the default) would cause the installer to delete a whole lo…

There's also this one from Pool of Radiance's 2001 release: http://www.rpgfan.com/news/2001/1416.html Uninstall wipes out your Windows directory.

I still have nightmares from this buggy mess. To add insult to injury the shop didn't want to take the game back afterwards.
Post reply on HN