in reply to Re: Should you use a module to hold configuration items?
in thread Should you use a module to hold configuration items?

Changing a module is not always trivial. Where I work it involves creating a document requesting permission for a change, a process which normally takes a week or two. Of course there are emergency requests you can process without outside discussion, to handle things that break at 2 am, but the discussion of why it was needed simply follows the change rather than precedes it. Then you have to unlock the source project, check out the file, change it, check it in, and distribute the changes to the production file system.

As Occam said: Entia non sunt multiplicanda praeter necessitatem.

  • Comment on Re^2: Should you use a module to hold configuration items?

Replies are listed 'Best First'.
Re^3: Should you use a module to hold configuration items?
by BrowserUk (Patriarch) on Sep 19, 2010 at 09:51 UTC

    If you have configuration files, that drive the actions and correctness of your applications, that are subject to less strict procedures than your source files, you have a gaping hole in your process.

Re^3: Should you use a module to hold configuration items?
by Jenda (Abbot) on Sep 19, 2010 at 09:13 UTC

    The important question is ... is changing a config file in a different format any easier?

    Jenda
    Enoch was right!
    Enjoy the last years of Rome.