[dead]
oh and it also hijacks back button
11–20 of 27 posts
[dead]
oh and it also hijacks back button
IME "real data work" doesn't involve notebooks.
By the end of it I might remove the notebook entirely but usually I keep it for some visualisation + running stuff as a cli tool.
This is one shot with Claude Code. What’s the moat?
Not the op or affiliated but. You really shouldn't and often cannot legally send off data or information about data to 3rd parties. Maybe schemas are okay but 1 mistake and your company can be in serious trouble. So local models is a good idea. This is a safer workflow if implemented correctly to prevent certain types of mistakes when LLMs inevitably hallucinate or make a mistake. That said, 200 usd? I don't believe…
the best you can do is show them the code and hope they catch mistakes. Data scientists who can't read code probably shouldn't be running AI generated analysis on real data.
Notebooks as the output format is funny because notebooks are famously bad for reproducibility. Out of order execution, hidden state, etc. You're solving "chat isn't reproducible" with a format that also isn't really
How does this compare to open source Deepnote[0]? We use the cloud version (BYOC) at my previous company to replace self-hosted Jupyter notebooks, and it's pretty great. [0] https://github.com/deepnote/deepnote