2 Jan
2013
2 Jan
'13
9:17 a.m.
In article <20130102143216.2ef9228809dd6ee38ddd0e0b at unixag-kl.fh-kl.de>,
Jochen Kunz <jkunz at unixag-kl.fh-kl.de> writes:
On Wed, 02 Jan 2013 10:54:28 +0100
Bert Thomas <bthomas at brothom.nl> wrote:
That is the time to spend on making it variable: when the customer
asks for it.
YAGNI doesn't say never do it, it says don't do it until you need it.
--
"The Direct3D Graphics Pipeline" free book
<http://tinyurl.com/d3d-pipeline>
The Computer Graphics Museum <http://computergraphicsmuseum.org>
The Terminals Wiki <http://terminals.classiccmp.org>
Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
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.