Main Content

Perl and Shell coding standards / costs of an IT project

Archive - Originally posted on "The Horse's Mouth" - 2007-09-11 08:16:30 - Graham Ellis

There are three major staff costs in the life of an IT project - the specification and development of the system, the maintainance and upgrading of the system though its life, and the investment that's made in data entry and integrity through the life of the system. And although there's a lot of thought put into the cost of developing a new system, that element is actually the smallest of the three. Ongoing upgrade / repair / maintainaince ends up costing more that the initial development. And the user's work on the data will end up being a bigger investment than the other two elements put together.

So it is important - REALLY important - to write the initial code in such a way that it can easily be amended through its life, and in such a way that it puts the user experience and efficiency as high priorities in the implementation. And to assist with that, a coding standards document is an excellent starting point and set of guidelines.

We have such a set of standards for Perl on our web site (here). And haveing such standards is particularly important for Perl - you'll see why on the standards description.

A correspondent writes:

"I am an employee in a CMM level5 company and I am asked to create a document regarding PERL and UNIX(shell scripts) coding standard.I found your site very useful to draft a document regarding PERL coding standards. Can you please provide similar help for preparing UNIX(shell scripts)."

And my reply:

I'm glad you found our site useful with regards to setting of Perl standards; it's a language in which programmers can write code that is utterly unmaintainable, as well as really clear and clean code, and a good set of standards should be at the core of any organisation's Perl strategy.

With regards to Shell programming, we don't have a similar set of documents available. Shell programs are typically much shorter and the issues of maintaining medium size to large scripts are far less common. In addition, the number of overlapping facilities and ability to shorten code in shell to the point it becomes hard to understand is far less. There are also numerous different shells, with each really needing its own set.

I'm afraid I don't have the free time to simply sit down and draw up a standard document, but I would be happy to put a day aside under our "extra" training scheme that would allow you and me to draw up a set of such standards together. The cost of such a day is 350.00 pounds + UK VAT at 17.5%. There are further notes on these days at (here).

The offer of mine is a real bargain - an astonishing offer in fact. But that's because I really want to help encourage quality coding. Here at Well House Consultants, we'll train you on not only how to program in Perl / PHP / Python / Ruby / Tcl, but also how to make the very best of those languages in writing maintainable code, with reusable modules / packages to save recoding, and with major thought to the user experience too.