Babylonian programming? #15
Description
I loved "Babylonian programming" but keep feeling it's strange to need a language/IDE feature.
Can't we simply have some regular code examples calling the function-under-test, and e.g. visualize the results live as we edit? 🤔 I.e. I prefer generic "live" support over specific "example" support.
-
However, skimming e.g. https://www.hirschfeld.org/writings/media/ReinLinckeRamsonMattisNiephausHirschfeld_2019_ImplementingBabylonianSbyPuttingExamplesIntoContextsTracingInstrumentationForExampleBasedLiveProgrammingAsAUseCaseForContextOrientedProgramming_AcmDL.pdf much of their goals are specifically about the ability to craft tools (?) Should read it carefully to see what I'm missing.
-
Example-driven development: bridging tests and documentation, video fleshes out a perspective on "examples" being better than "tests" by returning an object/state which you can explore live.
Here I'm more into functional than OOP, but I think conflating interaction<->code is a good start — just click at end of recorded example and keep interacting? Or perhaps it doesn't so much achieves that benefit as blurs the distinction 🤷♂️.