Ruth Holloway has been a system administrator and software developer for a long, long time, getting her professional start on a VAX 11/780, way back when. She spent a lot of her career (so far) serving the technology needs of libraries, and has been a contributor since 2008 to the Koha open source library automation suite. Ruth is currently a Perl developer and project lead at Clearbuilt. You can find out more about Ruth's passions and career at her site. She's a mother, grandmother, wife, artist, public speaker, and mommy to the cutest little dog you'll ever meet.
Ruth Holloway
| Follow @GeekRuthie
Houston, TX
Authored Comments
A look at the source code for Keyword::DEVELOPMENT will make it clear that you could *totally* use the same or a similar technique for other things.
Thirty years of writing code; I know all too well what happens when you hardcode config information. Which is why I said,"n the absence of a more evolved configuration management system." I've had a number of projects which started out with something like this, then iterated and got a more robust config management system, as the needs of the project became clearer.