David VujicRE: https://fosstodon.org/@pyconsweden/115944867558064453
How could I even develop things without the REPL and without the interactivity when writing code?
Part 2 of the blog post series by Jokim Tengstrand, about building a Tetris game step-by-step with Clojure and Python.
In this post, Joakim use REPL Driven Development and a functional programming style in both languages to develop the game.
https://tengstrand.github.io/blog/2026-01-11-tetris-playing-ai-the-polylith-way-2.html
#python #clojure #polylith #functionalPrograming #tetris #repldrivendevelopment
Large Language Tofu Model#TIL that #Julialang has a #REPLDrivenDevelopment very similar to #Clojure. You can send functions, code blocks or files to the REPL for evaluation. That's pretty amazing!
How is the library ecosystem for Julia? I know there are fewer libraries⦠but are they well maintained, and not as broken as with Python for example?
π Introducing python-tap - a tiny Python library useful for REPL Driven Development
Useful when running code on your local machine. With this tool, you can store and process data, such as function input parameters or local variables. This is useful when inspecting code and flows, and when running code in a REPL. You will have all the tapped data available in the session.
Yes, it is inspired by "tap>" in Clojure!
How fast can we get useful feedback on the Python code we write?
https://davidvujic.blogspot.com/2025/04/feedback-loops-in-python.html
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
REPL Driven Development in Python with emacs
Alessandra SierraDevelopment 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.
https://github.com/stuartsierra/component.repl
#SoftwareEngineering #BitRot #Clojure #REPLDrivenDevelopment
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
During the holidays, I have been experimenting and learning some Emacs Lisp. That was fun! I wrote a post about it and how I use it when writing Python code:
https://davidvujic.blogspot.com/2025/01/better-python-developer-productivity-with-rdd.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.