14 ms·
I heard of this technique, but unfortunately I don't see how it can be easily applied in software engineering/devops. Also, I now realized that aviation checkl
by akavel 4y ago
I heard of this technique, but unfortunately I don't see how it can be easily applied in software engineering/devops.
Also, I now realized that aviation checklists seem to tend to be done similarly with gestures - at least from what I saw on YouTube, not sure if that's representative or only used during education (?)
- samus 4y agoSpelling out loudly the command you are about to execute and explaining the reasoning behind it can help a lot too.
- akavel 4y agoOk, but am I to do it on every single command I do on my terminal? Or on which ones specifically? If the problem we're trying to solve is that I can sometimes overlook the "dangerous commands" among "safe ones", by definition of overlooking it won't work if I tell myself to "spell out the command only in case of the dangerous ones", no? I'm honestly trying to think of the way how I could approach this for myself, just I don't see a clear solution yet that wouldn't require me to spell out everything I type in my terminal window.