Earlier quoted context omitted.
Notebooks allows you to have snippets of code next to the historic results of their execution It is not just litterate programming, but more like an IDE that does not require your code to keep working (CI/CD... ) : you can refactor at your own pace, iterate, introspect past results, etc. You prototype like crazy, iterate much faster, and can tweak much more. However, notebooks are not popular with many programmers. T…
This isn't data science. The output of a playbook is dependent on a huge amount of external dependencies and state, and the execution can conditionally depend on that. Maybe programmers should use notebooks more (and I have no opinion on that) but this isn't a situation where they would confer much benefit.
External dependencies, state etc will all be handled, once excution is ironed out