Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!1.eu.feeder.erje.net!newsfeed.freenet.ag!newsfeed0.kamp.net!newsfeed.kamp.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.lang.c++ Subject: Re: Concrete classes considered harmful Date: Tue, 14 Jul 2015 08:52:14 +1200 Lines: 20 Message-ID: References: <8Ladnd8lHdolXjzInZ2dnUU78dGdnZ2d@giganews.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net mkzAwn0JR3+96MTHSNdSwwrWQrGH/7riDM53TgkBaW7K0jTCf0 Cancel-Lock: sha1:AnYT8IRWS9Wv0JDfcNBVOwKIt8A= User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:17.0) Gecko/17.0 Thunderbird/17.0 In-Reply-To: Xref: csiph.com comp.lang.c++:37067 Richard wrote: > > Ian Collins spake the secret code > thusly: > >> I agree. No one who uses TDD writes brain-dead isolated tests. > > I'm not sure what it means for a test to be "brain-dead isolated". > > However, there are plenty of times when I've started with tests and > gotten to a good design without designing up-front any interfaces or > abstractions explicitly. Did I have an idea of where I wanted to go > in my head? Sure, but I didn't write it down as a "design document". I've been down the same path many times, especially what doing XP for one.. In bigger projects some minimal up-front interface design is necessary. -- Ian Collins