# Misconceptions about REPL-driven development **URL:** https://clojureverse.org/t/misconceptions-about-repl-driven-development/6988 **Category:** Watercooler **Created:** [January 5, 2021, 12:04am UTC](https://clojureverse.org/t/misconceptions-about-repl-driven-development/6988 "2021-01-05T00:04:34Z") **Posts on this page:** 1 **Showing post:** 21
### Author: ![plexus](https://clojureverse.org/user_avatar/clojureverse.org/plexus/32/6_2.png) [@plexus](https://clojureverse.org/u/plexus) #### Post date: [January 12, 2021, 9:44am UTC](https://clojureverse.org/t/misconceptions-about-repl-driven-development/6988/21 "2021-01-12T09:44:30Z")
I have personally become convinced that REPL-driven development is a terrible name for what we do, precisely because of the reasons outlined above. People associate “REPL” with a specific place where you put code, but it’s not about the REPL as a place, that is entirely secondary, it’s about the interactivity that is possible when communicating with a live process. We don’t need to invent new terms for this, we just need to go back to the roots. This has been known since the 70’s as **interactive development**. Here’s a [paper from 1978](http://www.softwarepreservation.org/projects/interactive_c/bib/Sandewall-1978.pdf) that digs into what that means. (hat tip to @jackrusher for that). --- _[View the full topic](https://clojureverse.org/t/misconceptions-about-repl-driven-development/6988)._