Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!us.feeder.erje.net!feeder.erje.net!eu.feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.programming Subject: Re: programmer's keyboard Date: Sat, 29 Dec 2012 11:42:19 +1300 Lines: 15 Message-ID: References: <150e1c64-726a-43cc-82f9-a52c81a2e8ce@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net hdmJZ7z2yQxnfflYk1DFHgxLDHhU840PEJjuJIlbCa/KzgaR1OPGEHHMW4SLc+eVc+ Cancel-Lock: sha1:qw0GxheHtE+JWWHe3bNrr17gnRU= User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:17.0) Gecko/17.0 Thunderbird/17.0 In-Reply-To: Xref: csiph.com comp.programming:2673 BartC wrote: > "Robert Wessel" wrote: >> >> Some attention to detail is expected in this profession. > > Well, it reduces productivity. If I'm writing in C, and want to quickly > print out some data structure I've just filled in to make sure it's worked > properly, I might have to write something like this: If I want to make sure something works properly, I write a unit test. If I want to make sure my application does what the customer wants, I write rather a lot of them.... -- Ian Collins