Sorry for asking a dumb question, but how is this different from using Jupyter to write your interactive documentation/runbooks and interactive tests?
- it’s collaborative (think Google docs for code) when several people are working on the same instance of a livebook;
- it’s easy to extend with so-called smart cells (which are essentially pieces of gui you can inject in your document https://news.livebook.dev/v0.6-automate-and-learn-with-smart... ). Smart cells are available for various tasks (db connection/ interaction, data frame exploration, ML tasks, maps), and building your own is relatively easy;
- you can turn a notebook into a web app ( https://news.livebook.dev/deploy-notebooks-as-apps-quality-o... )
- you can run your code an a remote elixir node by attaching to it (although this requires some knowledge of distributed elixir/erlang )
[1] https://github.com/jonatanklosko/notebooks/blob/main/article... [2] https://github.com/livebook-dev/livebook/blob/main/lib/liveb...
It requires you to run a far less common tech stack and limits your hiring to a vanishingly small subset of developers.
Paradoxically, that may be a good thing.
Jupyter outputs JSON.