Type in the exact number of machines to proceed

Post by MaxBarraclough » Tue, Oct 27, 2020, 10:32 PM UTC

morelisp wrote: post #178

js2 wrote: post #99

Earlier quoted context omitted.

I learned a technique from a gray beard[0] when I worked as a student sys admin for the CS dept over two decades ago. Whenever typing a destructive command, he'd take his hands off the keyboard and drop them to his side, re-read the command, then put his hands back to press enter. I do this whenever I'm on a production server (which is rare anyway). I use different colored prompts for local and remote shells. [0] Tec…

A similar tip I picked up long ago: If you're typing a dangerous command, first type a `#` (or `--` if it's SQL, etc.), then the command. Then read it. Then go back to the start of the line and remove the comment and run it.

Post by eljimmy » Tue, Oct 27, 2020, 10:34 PM UTC

jlmorton wrote: post #180

brundolf wrote: post #127

Earlier quoted context omitted.

I've only been in the job field for six years, and yet: My first boss accidentally deleted our QA database, meaning to delete a local copy A later boss accidentally deleted our production database, thinking it was the clone that he had just made (which luckily we still had) Both of them were very experienced developers in their 40s. Nobody is beyond this kind of mistake.

War story time. Long ago, I worked for an interesting company that insisted on running its entire business on Linux desktops, all the way back between 1999-2002. Imagine running StarOffice/OpenOffice, Thunderbird, Netscape Navigator, etc, for your entire business back in 2000, including your executive team, marketing teams, everyone, most of whom had never even heard of Linux before. Anyway, this being Linux, everyon…

Post by waterhouse » Tue, Oct 27, 2020, 10:38 PM UTC

blantonl wrote: post #21

MaxBarraclough wrote: post #13

Earlier quoted context omitted.

Worth mentioning that, assuming the single study on the matter can be believed, the pointing and calling method is extremely effective in reducing the incidence of silly mistakes (that is, mistakes made in simple routine tasks, by competent individuals). Unfortunately, it strikes many as looking rather silly, so it hasn't been widely adopted.

Watch and listen to pilots as they complete checklists. They point and callout each item, switch setting, etc.

Post by tsomctl » Tue, Oct 27, 2020, 10:47 PM UTC

leetcrew wrote: post #91

dheera wrote: post #40

Earlier quoted context omitted.

> I've seen this called "pointing and calling" [1], Japan's train drivers use the technique to force themselves to perform actions and take notice of the current environment. The concept makes sense, though I don't quite fully get how to translate it to other contexts besides train driving where unexpected and unpredictable events come up all the time. Let's say you're driving a car and the traffic light turns red. D…

I don't think it really applies to stuff like driving, which almost has to be muscle memory to work at all. even with something routine and non-urgent like switching gears in a manual, the steps have to happen faster than you can say what you're doing. a good example from normal life is (physical) key management. I used to always forget my keys when walking out the front door, which was a big problem since it locks a…

Post by regularfry » Tue, Oct 27, 2020, 10:48 PM UTC

BalinKing wrote: post #176

morty_s wrote: post #65

Earlier quoted context omitted.

Came here for this. A: “Passing control” B: “Taking control” A: “You have control” B: “I have control” This is how I remember it (6174, UH-1Y).

As a fun fact, I was taught a shorter version (during private pilot instruction): "You have the control." "I have the control." IDK if it changes between aircraft types, commercial/private/military cultures, or if it's just coincidence.