Following up on my work with trying to make Python development more interactive with REPL Driven Development (previously posted article "Are we there yet?").
I recorded a very much improvised video 
I demo the setup and the workflow. Starting up a Jupyter kernel, connecting to it from my code editor, and modifying a running program.
About 13 minutes:
https://youtu.be/nJC9EVHjI24?si=SpRb-O7aRRGcdV5e
Development cycle time decays just like anything else in software. If not actively maintained, it gets worse over time.
I've worked on Clojure development cycles with tools.namespace and Component, but it's still hard: You have to intentionally design your code for interactive development and be careful not to break the feedback cycle.
A while ago, I wrote an article about my attempts to make development in Python more interactive, more "test" driven and more fun.
My North Star is the developer experience in Clojure, where you have everything at your fingertips using REPL Driven Development.
One thing that I haven't been able to figure out until now, is how to modify and evaluate Python code from an actual running program - without any restarts.
https://davidvujic.blogspot.com/2025/03/are-we-there-yet.html
I'm working on some Emacs Lisp code to make REPL Driven Development a nicer experience in Python. Since before, I do this already by sending code to an IPython shell buffer (old blog post in thread).
But I have always missed the nice DevX from Cider & Clojure, where the evaluated result is displayed right next to where my eyes are focused on (the current line of code).
I hope to be able to develop a package (or maybe just a config) shortly.
