On 3/1/2009 7:38 PM, Darren New wrote:
> This is kind of what inspired the question to start with:
>
>
http://gojko.net/2009/02/27/thought-provoking-tdd-exercise-at-the-software-craftsmanship-conference/

Interesting... this kind of goes along with the fact that many 
programmers tend to add features not needed, on the assumption that they 
may, one day, be needed.  Coding for future problems, rather than the 
one at hand :)

I read a blog post from someone (can't remember who at the moment) who 
stringently told his programmers to always specific code, even if they 
were certain that a general case method would be useful later on.  90% 
of the time, they never ended up using the general case methods.

Instead, he said they could write a simplified general case after they 
already used the same functionality in two separate projects.  Once they 
used it in three separate projects, then they were allowed to do a full 
design cycle on it and add it to the company's other libraries.

-- 
...Chambers
www.pacificwebguy.com

Post a reply to this message