Maintaining Code While Staying Sane

Date: Sunday, October 12, 2008 09:00 AM
Duration: 290 minutes

You can find more information on the following site:

Have you inherited a hideous lump of code that would need an exorcism before you could get it to run under 'use strict'? If you've acquired Perl code written by someone else, or even if your own code is giving you problems, this tutorial is for you. Based in part on Scott's book Perl Medic: Transforming Legacy Code (Addison-Wesley, 2004), it provides first aid for the ailing program that just landed in your lap. Don't be the victim of someone else's poor programming skills - be the hero by tackling and taming the legacy code beast!

Perl is easy to start using. But sometimes being easy can get you into trouble. The many ways to program in Perl mean that Perl code can often be cryptic, obscure, or muddled; just because a program runs doesn't mean it's maintainable. Hordes of programmers have acquired just enough Perl knowledge to get a program to run, and then one day, you find yourself tasked with maintaining one of those programs, and the horror begins.

This tutorial is designed to help you deal with that horror. You'll learn how to:

* Retrofit tests and profiling onto legacy code
* Get bad code to conform to best practices
* Make code warnings- and strict- compliant
* Recognize different Perl styles and deal with them
* Use tools to detect and remove duplication
* Make sense of code messes
* Understand and edit code at micro and macro levels
* Deal with political and interpersonal issues of code inheritance
* Make your own code more maintainable

Target audience: beginning through intermediate Perl programmers.

Copyright © 2006-2008 Pittsburgh Perl Mongers. Mast photo by whobee@flickr.