Why is it a bad idea to write configuration data in code?

Question

Real-life case (from caff) to exemplify the short question subject:

$CONFIG{\'owner\'} = q{Peter Palfrader};
$CONFIG{\'email\'} = q{peter@palfrader.org};
$CO         


        

Answer 1

Reason 1. Aesthetics. While no one gets harmed by bad smell, people tend to put effort into getting rid of it.

Reason 2. Operational cost. For a team of 5 this is probably ok, but once you have developer/sysadmin separation, you must hire sysadmins who understand Perl (which is $$$), or give developers access to production system (big $$$).

And to make matters worse you won't have time (also $$$) to introduce a configuration engine when you suddenly need it.