[ale] Making the argument for many scripts vs one big one.

[Pete Hardie]

cyclomatic conplexity
the UNIX philosophy
modularity

plenty of other reasons to break a big task into small ones

Pete Hardie
--------
Better Living Through Bitmaps


On Wed, Jul 24, 2013 at 8:29 AM, leam hall <leamhall at gmail.com> wrote:

> Any supporting ideas for pushing the argument of "Use lots of small
> scripts for a big task, instead of one large one"?
>
> So far my thoughts are:
>
>
> Isolation of new, untested functionality
> Ease of use when only one part of the task is required
> Easier to introduce new programmers
> Ease of maintenance since you don't have to look past one screen
>
> Anything else?
>
> Thanks!
>
> Leam
>
> --
> Mind on a Mission <http://leamhall.blogspot.com/>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20130724/4cc3f791/attachment.html>