Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.011 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'true,': 0.05; 'algorithms,': 0.07; 'coding,': 0.09; 'debugging.': 0.09; 'deploy': 0.09; 'linear': 0.09; 'output,': 0.09; 'subject: [': 0.09; 'subject:features': 0.09; 'testing,': 0.09; 'debugging,': 0.16; 'doing,': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'peek': 0.16; 'periods': 0.16; 'thinking,': 0.16; 'utterly': 0.16; 'followed': 0.16; 'wrote:': 0.18; 'normally': 0.19; 'replacing': 0.19; 'typing': 0.19; 'code,': 0.22; 'programming': 0.22; 'text,': 0.24; "i've": 0.25; '(for': 0.26; 'required.': 0.27; 'developing': 0.27; 'header:In-Reply-To:1': 0.27; 'quickly': 0.29; 'programming.': 0.30; 'message- id:@mail.gmail.com': 0.30; 'that.': 0.31; "d'aprano": 0.31; 'steven': 0.31; 'trivial': 0.31; 'yes.': 0.31; 'fri,': 0.33; 'raw': 0.33; 'possible.': 0.35; 'something': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'shorter': 0.36; 'done': 0.36; 'entry': 0.36; 'two': 0.37; 'step': 0.37; 'button': 0.38; 'process,': 0.38; 'subject:]': 0.38; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'does': 0.39; '12,': 0.39; 'to:addr:python.org': 0.39; 'even': 0.60; 'save': 0.62; 'times': 0.62; 'more': 0.64; 'total': 0.65; 'holding': 0.65; 'subject:Important': 0.65; 'close': 0.67; 'brain': 0.68; 'overall': 0.69; 'to,': 0.72; 'jul': 0.74; 'click': 0.77; 'transfer': 0.82; 'execution,': 0.91; 'saving,': 0.91; '2013': 0.98 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=JpqAyG/9dFv68HqthgVf3x+xaew/d5ks36QFdmOfeb4=; b=k9kgiYuPWQNroeTCxuPU3eGHq8kWNt8Z2i0+tvnlQ4a1DvLc+JN09oIrwmjTaHTsQy TT2freSa128Xy19yw4kKInINJzsq5Rd9abWf7IprGRR/pG8/OWWUt8v8zILVRzk89no2 IIiOmKIirGh9XLnPlmqA40/kh5cESHBkBV5jzBLjGYW13sCfhUQ3gD2lftxyVBWzyFva YgeoVbuh9ENZAueb11cMbM0yvGTg+BgBEq++4/JgzQJEGkPAZ9jzWaZX9AMcB698IHyc C6StJlWnjd3xN6m6cHUAafP1bof1o+22g2noQLqiBi/3N4byZ1ERoWLbq75cwQ8dCmus Q6xA== MIME-Version: 1.0 X-Received: by 10.52.34.40 with SMTP id w8mr19562148vdi.7.1373597436860; Thu, 11 Jul 2013 19:50:36 -0700 (PDT) In-Reply-To: <51df6c56$0$9505$c3e8da3$5496439d@news.astraweb.com> References: <2fdf282e-fd28-4ba3-8c83-aaaace1201ec@googlegroups.com> <51df6c56$0$9505$c3e8da3$5496439d@news.astraweb.com> Date: Fri, 12 Jul 2013 12:50:36 +1000 Subject: Re: Editor Ergonomics [was: Important features for editors] From: Chris Angelico To: python-list@python.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 30 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1373597446 news.xs4all.nl 15925 [2001:888:2000:d::a6]:54501 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:50486 On Fri, Jul 12, 2013 at 12:39 PM, Steven D'Aprano wrote: > Big deal. I am utterly unconvinced that raw typing speed is even close to > a bottleneck when programming. Data entry and transcribing from (say) > dictated text, yes. Coding, not unless you are a one-fingered hunt-and- > peek typist. The bottleneck is not typing speed but thinking speed: > thinking about program design and APIs, thinking about data structures > and algorithms, debugging, etc. > > Programming is normally done in spurts of typing followed by longer > periods of thinking, testing, debugging. That's true, but it's still important to be able to type quickly. You spend a minute or two figuring what you need to be doing, then want to see the result as quickly as possible. The plan is in your brain; you need to transfer it into code, save it, compile it if you need to, deploy it to your test-box if you need to, trigger its execution, and see its output. That's a roughly linear process, so any time saved in any step is an overall saving, and the shorter the total time from brain to output, the more smoothly your debugging/tinkering will be. That's why I've spent time developing systems at work that reduce the times required. With a single keystroke (F7 in SciTE), I can save, compile (for the one or two components that actually get compiled), and deploy to test-box, and a quick SIGHUP via Upstart does the rest. I can try two or three iterations of something without "losing" what my brain's holding onto - more if it's a trivial edit. Poor typing speed, or replacing the F7 whack with a button click that demands a mouse, would damage that. ChrisA