From: b.scott@csuohio.edu   
      
   On Mon, 14 Mar 2016 22:02:50 -0700, Kay Shapero   
    wrote   
   in   
   in rec.arts.sf.composition:   
      
   > In article <1i041pi4ptf4e.1hzv5a41xrmk5$.dlg@40tude.net>,   
   > b.scott@csuohio.edu says...   
      
   >> I actually do understand that one: if one writes to find   
   >> out what happens, then once you find out, the story has   
   >> already been 'written', and finishing the actual writing   
   >> could be pretty boring.  It's a bit like suddenly realizing   
   >> how to solve a programming problem cleverly but finding the   
   >> details of coding a bore.   
      
   > Actually I've always found coding kinda Zen, and after I   
   > have worked out the desired algorythm, I can't wait to   
   > test it out (and besides, if I don't have to why should   
   > I want to risk someone else doing it Wrong?)   
      
   But for me the interesting part was usually working out the   
   method; at that point I knew that it would work if properly   
   coded.  Unless I was personally interested in the output,   
   I’d already obtained my reward.   
      
   [...]   
      
   > Do I miss assembler? Actually, no... :)   
      
   I probably wouldn’t if I were still programming, but 360   
   Assembler was by far my favorite language in that dim past   
   (late 1960s) when I actually did quite a bit of   
   programming, and I have fond memories of it.   
      
   Brian   
   --   
   It was the neap tide, when the baga venture out of their   
   holes to root for sandtatties.  The waves whispered   
   rhythmically over the packed sand: haggisss, haggisss,   
   haggisss.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)