Path: csiph.com!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: Java return intellityping? Date: Mon, 05 Nov 2012 08:07:05 +0100 Lines: 24 Message-ID: References: <4c12f491-2b3f-421b-b420-60d4220237d1@googlegroups.com> <9c8785cc-fd38-4e23-a7ba-4a3503edc3f5@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net e4GZ0kiXHFMxtZAD3ZQp0AIUS98TRFWLuA8iKH5n9Bb+wOTYKqMxPXVtMI04Bg3C4= Cancel-Lock: sha1:pw9ZD8W9m9zOH9aYAzJ1gVJs3nE= User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:19634 On 04.11.2012 18:47, Daniel Pitts wrote: > Often, most of my thinking is done before I start typing, whether it be > to use a shortcut or not. I find that although my available "thinking" > time may not be increased, the time-to-delivery is improved (decreased) > because of shortcuts. I can also use my knowledge that there *are* > short-cuts to allow my to defer thinking and decisions until a later > time. For example, I may be writing a class which might be better as two > classes, but it might not be. I know that I have refactoring tools, so > I'll start with the easiest to implement, and then consider refactoring > when it becomes relevant. ... which also can lead to the opposite effect: you end up changing the same logic so often that time actually increases vs. the variant where the absence of refactoring tools led you to do more thinking upfront and start coding later. Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/