4 ms·

This is a lot like the checklists a lot of industries use, just automated on your shell instead of being on paper. I'm thinking of a pilot's checklist, or an o

• mypalmike 5y ago
  There's a difference though. I've worked in ops teams where there were many such checklists in Word documents, wikis, or whatever. Standard procedures involved reading from these runbooks and following the steps. But here, you have code that plays the same role, but which can eventually be changed out with code that actually does the work for you. It's a seemingly small difference but it's actually huge if you have some decent developers who can spend a bit of time every once in a while pushing the needle forward in automating these manual steps. Another note: I've found that it's hard to even get teams to consider the minor change of using the code version instead of the wiki. Inertia is a real problem.