Live programming is a programming paradigm in which the programmer interacts with a running program, modifying its behavior in real time without stopping, recompiling, or restarting. Unlike the traditional edit-compile-run-debug cycle, live programming treats the program as a dynamic system that can be inspected, probed, and reshaped while it executes. The paradigm originated in Lisp's REPL-driven development and reached its most complete expression in the Smalltalk image, where the entire development environment was itself a live, mutable program.\n\nLive programming has re-emerged in contemporary systems through interactive notebooks (Jupyter, Observable), hot-reloading development servers, and real-time visual programming environments. The paradigm challenges the assumption that software is a static artifact constructed in discrete phases. It suggests instead that programming is a continuous, improvisational activity more akin to playing a musical instrument than to assembling a machine.\n\nThe resistance to live programming in industrial software engineering is not technical but organizational. Live systems are difficult to version-control, difficult to test in reproducible ways, and difficult to divide into modules that can be assigned to separate teams. The edit-compile-run cycle persists not because it is better but because it is more compatible with the bureaucratic structures of corporate software production.\n\n\n\n