On 17.01.2011 08:08, Gavin Beau Baumanis wrote: > Is the answer not; > Code to the manner that provides the greatest return on a developer's time > for THIS problem.
You have to take into account the cost of maintaining the code, too. For example, it's usually "fastest" to not worry about coupling and factoring, which makes the "fast" implementation usually a pile of copy-paste, impenetrable mess. Which costs a lot more in the long run, because sooner or later you have to untangle the mess in order to make any kind of improvement. Witness libsvn_wc and how long it took for anyone to dare throw it away and begin from scratch, because the original was simply not amenable to improvements. :) -- Brane
