2 Jan
2013
2 Jan
'13
5:32 a.m.
On Wed, 02 Jan 2013 10:54:28 +0100
Bert Thomas <bthomas at brothom.nl> wrote:
I had a guy working for me who spent several days on
adding a database
to a program to make everything in the program configurable. Most of the
configuration items would have done fine as a program constant IMO. The
others could have easily be set by commandline parameters.
IMO this is an example of overkill and I would fully understand it if
the customer was unhappy with the amount of "improvement" gained for the
costs involved.
Depends. By adding that "overkill" that programmer solved
the problem
once and for all. If he had it done as a constant, the customer may
wanted that constant to become a variable in a furure release. That
woud cause additional efforts. The code would need to be touched again.
But if it is already a variable read from a database, its just a matter
of adding e.g. a GUI knob for the variable.
Been there, done that. Many times. ;-(
--
\end{Jochen}
\ref{http://www.unixag-kl.fh-kl.de/~jkunz/}