Comments on: Scripting (part 3) - which language? http://blog.agilesysadmin.org/2009/03/15/scripting-part-3-which-language/ Discovering system administration best practices and tools Sun, 20 May 2012 14:34:29 +0000 http://wordpress.org/?v=2.2.1 By: Dave http://blog.agilesysadmin.org/2009/03/15/scripting-part-3-which-language/#comment-3161 Dave Sun, 09 Aug 2009 15:05:22 +0000 http://blog.agilesysadmin.org/2009/03/15/scripting-part-3-which-language/#comment-3161 http://everythingsysadmin.com/aboutbook.html is a a great collection of this kind of information. http://everythingsysadmin.com/aboutbook.html is a a great collection of this kind of information.

]]> By: Peter Tribble http://blog.agilesysadmin.org/2009/03/15/scripting-part-3-which-language/#comment-11 Peter Tribble Sat, 21 Mar 2009 15:42:36 +0000 http://blog.agilesysadmin.org/2009/03/15/scripting-part-3-which-language/#comment-11 While consistency sounds good in theory, in practice it is simply unsuitable. Given that different tools have different strengths and weaknesses, and the range of tasks to perform can be large and diverse, requiring consistency simply means that you'll be forcing the use of inferior solutions much - if not most - of the time. Using the best tool for the job invariably makes maintenance easier, because the tools are much simpler. I've seen a lot of unmaintainable code simply come from using the wrong tool - whether that be by mandate (following the consistency argument here, for example), or because it's the latest fad (or was featured on the cover of the magazine the CIO read last week), or because it's all the author knows. While consistency sounds good in theory, in practice it is simply unsuitable.

Given that different tools have different strengths and weaknesses, and the range of tasks to perform can be large and diverse, requiring consistency simply means that you’ll be forcing the use of inferior solutions much - if not most - of the time.

Using the best tool for the job invariably makes maintenance easier, because the tools are much simpler. I’ve seen a lot of unmaintainable code simply come from using the wrong tool - whether that be by mandate (following the consistency argument here, for example), or because it’s the latest fad (or was featured on the cover of the magazine the CIO read last week), or because it’s all the author knows.

]]>