4 ms·
I have mixed feelings on this one: Some organizations get checklist happy and make checklists for procedures which essentially can’t fail and which require
by _delirium 17y ago
I have mixed feelings on this one:
Some organizations get checklist happy and make checklists for procedures
which essentially can’t fail and which require no judgement. Those shouldn’t
be checklists — they should be shell scripts.
That's in principle the right thing to do, but shell scripts have this nasty habit of accumulating complexity, to the point where you end up with, say, a backup-and-restore process that everyone is afraid to change the slightest thing about, because nobody actually remembers exactly how it works (even if you wrote it yourself!), and the bash script has grown to be some opaque monster.
Maybe it could work to insist on very well-commented shell scripts, so well-commented that someone could use it as a checklist just by reading the comments, if they needed to. But then the comments have to stay in sync with what it's actually doing!
- lallysingh 17y agoPut it in version control. svn blame and the rev's log message should tell you want you want to know.