For 2023 - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.
Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!
I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
Avoid the wheel being re-invented by using Perl modules
"Don't re-invent the wheel". Such is the underlying philosophy of programming - if you re-write a piece of code that's already been written and tested, you're probably wasting time that could also be better used. You're also likely to be creating a longer term support issue - someone's going to have to look after your code in the future.
Am I discouraging you from writing new code? Yes, if the code already exists. But no - there are still things to invent.
Having invented something, you should make it as easy as possible for others to find and use it:
* You should be writing your Perl code for distribution in classes /modules. That way, you can encapsulate the logic that you need within the class and provide a neat and short way for users and other programmers to make use of what you've written.
* You should be using the structure that's already been defined (and become something of a standard) to add your documentation, test routines and support files to your class; this will package it in a similar way to that in which it would be uploaded to the CPAN
* You should publicise your module well so that it can be found easily by anyone who searches for it, even if they don't know exactly what they're searching for.
Samples of files that make up a standard module are available on our web site
and our Perl for Larger Projects
course will be updated to include extra coverage on this topic before the next public run in December.
I'm giving a Perl course tomorrow, which is why I'm thinking Perl today - but the philosophy described here applies to PHP and the PEAR, Python and the Vaults of Parnassus [[ or now - the Cheeseshop ]] and elsewhere too. (written 2004-11-08, updated 2006-06-05)
Associated topics are indexed as below, or enter http://melksh.am/nnnn for individual articlesP219 - Perl - Libraries and Resources 
Talk review - Idiomatic Perl, David Cross - (2004-10-12) 
Where do Perl modules load from - (2005-06-24) 
Use standard Perl modules - (2005-06-25) 
Why reinvent the wheel - (2006-05-06) 
Coloured text in a terminal from Perl - (2006-05-29) 
Self help in Perl - (2006-06-14) 
Judging the quality of contributed Perl code - (2007-06-06) 
Outputting numbers as words - MySQL with Perl or PHP - (2007-06-17) 
Ordnance Survey Grid Reference to Latitude / Longitude - (2007-10-14) 
Using English can slow you right down! - (2007-11-25) 
About dieing and exiting in Perl - (2008-11-01) 
Debugging and Data::Dumper in Perl - (2008-11-02) 
Do not re-invent the wheel - use a Perl module - (2009-06-11) 
Loading external code into Perl from a nonstandard directory - (2009-06-12) 
Operator overloading - redefining addition and other Perl tricks - (2009-09-27) 
Syncronise - software, trains, and buses. Please! - (2010-08-22) 
Expect in Perl - a short explanation and a practical example - (2010-10-22) 
The week before Christmas - (2010-12-23) 
What do I mean when I add things in Perl? - (2011-08-02)
Some other Articles
The next generation of programmerExpiration dates or times on web pagesRelative or absolute milkmanA Parallel for Perl 6Avoid the wheel being re-invented by using Perl modulesTraining notes available under Open Distribution licenseFriday, busy week!URLs - a service and not a hurdleA typical morningTaking Equipment offshore to run a course
4759 posts, page by page
Link to page ... 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96 at 50 posts per page
This is a page archived from The Horse's Mouth at
the diary and writings of Graham Ellis.
Every attempt was made to provide current information at the time the
page was written, but things do move forward in our business - new software
releases, price changes, new techniques. Please check back via
our main site for current courses,
prices, versions, etc - any mention of a price in "The Horse's Mouth"
cannot be taken as an offer to supply at that price.
Link to Ezine home page (for reading).
Link to Blogging home page (to add comments).