|
|
|
|
|
|
by akdor1154
1312 days ago
|
|
|
What would you go with instead for collaborative notebooks? I ask because normally I tend pretty strongly towards the "NO just let the DSes/analysts work how they want to", which in this case would be running Jupyter locally. However DBr's notebooks seem genuinely useful. Is your issue "but I don't need Spark" or "i wanna code in a python project, not a notebook?", or something else? Imo if DBr cut their wedding to Spark and provided a Python-only nb environment they'd have a killer offering on their hands. |
|
|
Production workloads should be code. In source control. Like everybody else.
Notebooks inevitably degrade into confusing, messy blocks of “maybe applicable, maybe not” text, old results and plots embedded in the file because nobody stripped them before committing and comments like “don’t run cells below here”.
They’re acceptable only as a prototyping and exploration tool. Unfortunately, whole “generation” of data scientists and engineers have been trained to basically only use notebooks.