|
|
On 10/09/2012 09:51 AM, scott wrote:
>> I take it you don't subscript to "test-driven software development" as a
>> methodology either? ;-)
>
> Sure, do tests, but properly design the stuff first (including the
> tests). You shouldn't use testing as a substitute for good design.
Amen.
> You think the latest machines are more efficient and better at cleaning
> by magic?
No. I think they aren't any more efficient at all.
> You could use the same argument for car engines, just take the previous
> one, add a couple of trivial differences and test it. But again nobody
> would buy your new car because all your competitors would have spent the
> last 5 years designing a far more efficient engine (even if it looks the
> same from the outside).
Surely trying to tune an engine to get a few percent more efficiency out
of it is vastly easier than INVENTING the internal combustion engine in
the first place...
Post a reply to this message
|
|