Where the work is done.
WHAT NOTEBOOKS PROVIDE
Interactive exploration Output alongside code Visualisation in place
WHAT THEY SUIT
Exploration, analysis and explanation.
WHAT THEY DO BADLY
Reproducibility, since cells run in any order Version control, since output is embedded Testing Reuse
WHAT HIDDEN STATE MEANS
Variables defined by cells since edited or deleted.
WHY THAT IS DANGEROUS
A notebook can work while its code, run fresh, does not.
WHAT TO DO PERIODICALLY
Restart and run everything, to verify it works.
WHAT TO MOVE OUT OF NOTEBOOKS
Anything reused Anything that will run unattended Anything requiring testing
WHERE TO MOVE IT
Modules, imported into the notebook.
WHY THAT WORKS WELL
Exploration stays interactive while logic becomes testable.
WHAT TO NEVER DO
Schedule a notebook as a production job.
WHAT TO CONFIGURE
Version control, with output stripped A consistent environment definition A formatter and linter
WHAT REMOTE DEVELOPMENT PROVIDES
Working against capable hardware from a modest machine.
WHY THAT MATTERS LOCALLY
It avoids needing expensive hardware locally.
