[HN Gopher] Conversational software development (2020)
       ___________________________________________________________________
        
       Conversational software development (2020)
        
       Author : pmarin
       Score  : 28 points
       Date   : 2023-03-22 13:06 UTC (9 hours ago)
        
 (HTM) web link (oli.me.uk)
 (TXT) w3m dump (oli.me.uk)
        
       | 32gbsd wrote:
       | This seems like just another tool to add to my tool box. Maybe it
       | helps someone
        
       | twobitshifter wrote:
       | Could use an example of how this workflow is superior to having a
       | debugger drop in repl like you can do in many languages. For
       | example pry for ruby or debugger in chrome, which allow you to
       | interact with the code in it's current state. With lisp i think
       | the benefit is you can evaluate as you go and skip debugging all
       | together.
        
       | SlimTim10 wrote:
       | I find Haskell is really good for this. Typed holes + ghcid makes
       | for a really fast and helpful feedback loop.
        
         | marcosdumay wrote:
         | Ghci is a really impressive REPL, with very fast reloading and
         | very complete metadata handling. Also, it's easier to handle
         | conversations about pure code.
         | 
         | But most languages have many features aimed at it. The captcha
         | is that it tends to come bundled on the debugger, instead of in
         | a separate tool. That makes many people fail to recognize them.
        
       | gorjusborg wrote:
       | We don't care about the REPL itself, rather that the language is
       | 'image based' (see
       | http://c2.com/wiki/remodel/?ImageBasedLanguage).
       | 
       | Also, very cool to see reference to Conjure on HN. That plugin is
       | very impressive.
        
       | john-tells-all wrote:
       | Fast feedback loops!
       | 
       | In my Fast Development workshop I recommend:
       | 
       | Goals are _speed_ (low latency developer feedback), and _quality_
       | (create something the client expects and values).
       | 
       | Speed: use `entr` or another tool to automatically run tests when
       | a file changes.
       | 
       | Quality: "test" first -- write a test before code, if you have to
       | think about the code. In this way you get high-level dev
       | feedback, before the code is written.
       | 
       | Quality: use the system to calculate your function's result. Then
       | either use "assert 0, value" to emit the result to you the
       | developer, or use the debugger. In either case the computer does
       | the work and you get feedback.
       | 
       | The above three-part process is similar to the OP,
       | "conversational" is a good term for it.
        
       ___________________________________________________________________
       (page generated 2023-03-22 23:01 UTC)