Documentation and automation

In addition to my article about documentation and automation, I found an interesting statement in the book "The Practice of System and Network Administration". The author of chapter 9 ("Documentation") stats:

Documentation is the first step to automation: If you don't know exactly how you do something, you can't automate it.

I haven't thought of it this way before. In my opinion he is right, but I think you don't have to write the documentation on paper, but you must have some sort of documentation in your head to automate a task. It can be easier to write a script and test it with a written documentation. You can use your documentation as some sort of pseudo code.
Another sort of documentation, your command history, is also a good starting point for automation (also mentioned in this chapter).


Post a Comment