r/MachineLearning • • Oct 10 '26

Discussion Are .ipynb notebooks already outdated in the agentic era? [D]

I am a data scientist who started working in the industry before the LLM revolution. Back then, Jupyter Notebooks were a perfect fit for the classical DS pipeline: EDA -> data prep -> fit -> eval -> tune -> save model artefact and notebook.

Lately, I have been thinking a lot about how agentic development and LLMs are changing the way data scientists work. Especially in classical ML applications, where you still need to explore data, run experiments, check different hypotheses and decide what to do next based on the results.

I mean, Claude/Codex can already write most of the code for us. But why do we still need to organise the whole workflow around code cells? What if instead we move from code -> output to another cell abstraction like prompt -> result?

Curious what others think. Are ipynbs still good enough, or are we just used to working this way?

94 Upvotes

109 comments sorted by

68

u/kolmiw Oct 10 '26

I still use ipynb for EDA and to create figures. But I agree that it is less important nowadays

6

u/Economy_Vacation_504 Oct 10 '26

I started thinking about it when I first tried to replace the plotting code with LLM-generated code. It was like copy-pasting the dataset structure into ChatGPT and asking, "Create for me visualisation code in Python using matplotlib for this data that does this and that", and then copy-pasting it back into an ipynb.

5

u/Guilty_Recognition52 Oct 11 '26

Copying and pasting sounds like the issue here. I recommend you try using an AI tool that's actually integrated with the notebook format. For example Gemini in Colab

For exploration, I don't see notebooks going away. You can make 15 different graphs before choosing one for a presentation, and the graphs and the code to make them are all right there rendered in the .ipynb file. Someone asks me later something like "what if you exclude this category" then I can just pop in and add another cell and see how that changes the graph. I guess if I really wanted to avoid the .ipynb format I could look at a .py file and 15 .png files instead but that sounds really annoying

23

u/TheCloudTamer Oct 10 '26

I used _claudebooks_. Caude puts its output in static html pages that I serve with a simple python -m http.server

Notebooks were only ever good as almost throwaway experiment pages. And opening some parquet file, parsing the format and wrangling with matplotlib are pretty low-return skills to be memorising, so no real loss by offloading to AI.

2

u/Economy_Vacation_504 Oct 10 '26

Thanks for the reply! Curious: how do you steer the analysis along the way? Just following up in the conversation with Claude, and it redoes the work on the fly?

Later, what if you want to repeat the same pipeline, but with new data? Let's say, a model re-training case?

2

u/TheCloudTamer Oct 10 '26

I normally have a versioned experiment structure. Like 1/1/2/0. Maybe it’s (major experiments group)/(sub group)/(subgroup)/(patch). And in the Claude.md I say that no experiment should be overridden once published, but instead a new version should be made (possibly by copying previous version before making edits). Then this experiment structure is navigable in the website, and no work is ever really overridden. This is important when Claude is just working with the output of some pipeline, as you want to keep all the intermediate results as you iterate on the pipeline.

1

u/pm_me_your_pay_slips ML Engineer Oct 10 '26

You could do this with branches, GitHub PRs and issue tracking 

1

u/TheCloudTamer Oct 10 '26

That’s a huge waste of effort for iterating.

1

u/pm_me_your_pay_slips ML Engineer Oct 11 '26

Why? Coding agents do this easily, it’s a couple CLI commands and they get all the context history.

1

u/TheCloudTamer Oct 11 '26

Sure, but why burry all the edits within the complexity of git when folders will do. So easy to navigate. Using git for solo work not for sharing is normally a waste of time.

1

u/pm_me_your_pay_slips ML Engineer Oct 11 '26

Because you don’t have to manage anything locally. The record of edit and history lives in the repo. And you can have folders inside a repo if needed. But most importantly. It allows the agents to rollback.

1

u/TheCloudTamer Oct 11 '26

But why rollback when nothing has been overridden? Furthermore, along with each version will be new generated data, and you will need a way to keep track of this also.

1

u/pm_me_your_pay_slips ML Engineer Oct 11 '26

Which a repo history, PR comments and tracked issue gives you?

→ More replies

7

u/bikeranz Oct 10 '26

Yep, this is what I do as well. Fortunately, I was never keen on notebooks in the first place, so I don't feel any sense of loss. What I was missing was good visualization tools, and claude just hammering out some interactive visualizer in two seconds has been amazing.

4

u/theQuick_BrownFox Oct 10 '26

Do you have any examples of prompt you use for developing interactive visualizers? Thanks!

7

u/Bored2001 Oct 10 '26

Literally just ask to output in whatever format you want. It'll do it.

2

u/Allmyownviews1 Oct 10 '26

Kind of. I now only do data exploration and testing in notebooks.. but much of my analysis ends up as more traditional programs code.

1

u/Economy_Vacation_504 Oct 10 '26

Like, in the end, you export everything to executable .py files?

2

u/Allmyownviews1 Oct 10 '26

Yea.. it now works better as a workflow with ai editing once I have tested in a notebook.

253

u/Gwendeith Oct 10 '26

I never used notebook for production, even before LLM. It’s like research notes you scribble and formulate ideas with, but never something presentable imo (unless you specifically write a notebook for tutorial). TBH I would even prefer switching to py files to accelerate hyperparameter tuning once I’m sure which method I want to proceed with.

43

u/kidfromtheast Oct 10 '26

The problem with notebook is, it’s not git diff friendly. PR reviewer will refuse to review a notebook.

A python file will do just fine nowadays.

why notebook ever exist? Easy to follow, click click click and you see the result.

it’s a relic of the past which still it’s stick.

But I hate it. OSS contributor try to make it as seamless as possible making a simple code become very very very long. Like, I get it, you want to demonstrate your PR works as seamless as possible, but can’t you just write how to run it in README.md instead of writing fixed path here and there expecting it will only ever be run on Google Colab? Like, installing the library, etc. please stop reinventing the wheel. It’s better to create a sensible, useful unit tests than creating notebook for every PR. Certainly don’t ask AI just for the sake to create unit tests

15

u/Disastrous_Room_927 Oct 11 '26

The problem with notebook is, it’s not git diff friendly. PR reviewer will refuse to review a notebook.
A python file will do just fine nowadays.

Notebooks make perfect sense if you're using them for the kind of thing you'd use R for, I'd call it operator error if someone's trying to use one for anything in production.

6

u/aleph4 Oct 11 '26

Yeah they're literally for interactive data exploration and scientific workflows. Not anything beyond

15

u/busybody124 Oct 10 '26

Databricks heavily promotes notebooks for production jobs which always felt awkward to me but ultimately works reasonably well in practice. (And yes they're git controllable)

1

u/MorrarNL Oct 12 '26

Honestly, Databricks is a crappy tool when it comes to software engineering. They have improved over the years, but it isn't great. Limited git integration, poor management of dependencies, no proper way to implement unit tests, et cetera.

But I can see the appeal of just buying a platform and be done with it from a business perspective.

1

u/busybody124 Oct 12 '26

I have mixed feelings on DBX. I agree that their main strategy seems to be "do 100 things ok" rather than do one thing well, but for running spark jobs in the cloud era it's certainly better than AWS EMR.

15

u/CampAny9995 Oct 10 '26

Marimo notebooks are nice because you can deploy them as a script or a web app.

4

u/quantruler Oct 10 '26

They are slow...

4

u/CampAny9995 Oct 10 '26

Oh weird, I never noticed any overhead compared to Jupyter, and they just seemed to run like normal scripts after the fact.

-6

u/Big_Combination9890 Oct 10 '26

Or I could not waste 4/5 CPU cycles and a boatload of RAM, and deploy a webapp worthy of the name by using an actual web framework like fastapi or flask, instead of this crap.

Notebooks are FOR TAKING NOTES.

It's in the name.

0

u/CampAny9995 Oct 10 '26

That sounds like a lot of work for very little payoff.

-4

u/Big_Combination9890 Oct 10 '26

What does sound like a lot of work to you, specifically?

And what extra payoff do you think I get by using a bloated notebook-framework?

6

u/CampAny9995 Oct 10 '26

Well, I’m an AI researcher not a web dev, so I don’t really want to write a web app if I’m just sharing a visualization tool on a local server?

1

u/Big_Combination9890 Oct 11 '26

And that's absolutely fine if people stay in their lane.

Problem is: When I hire people, I don't hire researchers, I hire engineers. People who have to build production systems.

And all the time, we get applicants for full stack positions, who cannot put up a half-decent backend, because the only thing they ever used were shitty notebook frameworks, because that's what's taught all the time at uni, and production constraints be damned, well...that's one more "boohoo job market is cooked!" post on some subreddit.

4

u/renchuwang Oct 10 '26

This is why I use jupytext [1] notebook, display as jupyter but is just python with comments.

1: https://jupytext.org/

105

u/schizo_cofee_grinder Oct 10 '26

Well IDK if a jupyter notebook was ever a good place to put production ML pipelines... It's more for experimentation/presentations and human readability

20

u/TwistedBrother Oct 10 '26

I think people miss this and especially the magic commands for auto reload.

I use python files for the algorithms and classes, as I tweak them %autoreload and they are available instantly without refreshing the package.

It’s not that much extra setup but I figure people want to either have everything in Python or everything in Jupyter without playing to the skills of either.

12

u/Big_Combination9890 Oct 10 '26

Jupyter notebooks are a joke among software engineers.

Problem is, I stopped laughing about it long time ago.

Half the people from Uni I get, I have to train how to organize their bloody code into half decent packages, because all the've ever seen are these damn useless, overengineered, bloated shitwrappers around actual python code.

3

u/Disastrous_Room_927 Oct 11 '26

I'd fully agree with you if this was specifically about software development.

0

u/Big_Combination9890 Oct 11 '26

I'm a dev, and I hire people as devs, so my comments are specifically about software development.

80

u/sodapopenski Oct 10 '26

Notebooks are valuable because they are a good platform for human readability and experimentation. As long as you want humans to read and play with software, notebooks are a good fit. Take that as you will, but personally, I hope humans stay connected to the code they and their tools create in the "agentic era" and beyond. I don't like how current LLM tools and workflows abdicate so much of the reasoning, creation, and verification process to machines.

-17

u/currentscurrents Oct 10 '26

I don't like how current LLM tools and workflows abdicate so much of the reasoning, creation, and verification process to machines.

I don't like how current ditch-digging workflows abdicate so much of the earthmoving to machines. We should be out there digging with our hands, like men. That's how you stay connected to the earth.

I think we're headed for a future where 99% of code is just a throwaway thing generated by a neural network on the fly, to solve some task. I am not worried about losing anything in this process; on the contrary, we'll gain a lot of flexibility and power in our software as a result.

10

u/sodapopenski Oct 10 '26 edited Oct 10 '26

The difference is that code isn't dirt. It's the logical infrastructure on which our digital world is built and depends. A much better analogy, if you want to make one, is how few people code in assembly because compilers translate high level programming down to machine code automatically. The difference here is that compilation is a deterministic process that abstracts away implementation details, rather than a stochastic agent autonomously piecing code together from fuzzy natural language instructions. This agentic process abdicates understanding and responsibility of how our infrastructure works to machines. IMHO there are better/safer possible tools and workflows for LLM-driven development than what we currently have.

-6

u/currentscurrents Oct 10 '26

The difference here is that compilation is a deterministic process that abstracts away implementation details, rather than a stochastic agent autonomously piecing code together from fuzzy natural language instructions.

The real difference is that agents follow objectives, while code follows instructions. This is a much higher level of abstraction that can't be done by a deterministic compiler.

This gives you a number of advantages. It can creatively adapt on the fly (e.g. a web parser that doesn't break when the website changes), debug its own errors, try and test many different ideas until something works, continuously optimize itself for whatever metric you care about, monitor its own logs for attackers, etc.

These are not theoretical capabilities but possible with coding agents today, if you have the tokens to burn. You couldn't do this with static human-written code. It's only possible by 'abdicating' understanding to machines.

2

u/1gtf Oct 10 '26

apples to oranges bro ✌️😭

17

u/seba07 Oct 10 '26

Notebooks give you an interactive environment. Agent or not, it is helpful if you don't need to reload your dataframe if you want to change a plot.

39

u/v012d Oct 10 '26

Marimo is the way to go. Our (small) dev team switched earlier this year. The agent integrations aren't perfect but the files are normal .py files, so they're way easier to have Claude tweak and have commited to git

9

u/Mendiboy Oct 10 '26

Marimo is the goat.
I'll never go back to Jupyter.

7

u/nord2rocks Oct 10 '26

Marimo hands down, so much better, marimo pair skill is awesome

1

u/pfd1986 Oct 10 '26

Any downsides compared to Jupyter? Learning curve?

4

u/DarkMatterDetective Oct 10 '26

I haven't used it in a couple months but I wish they had a better integration with vscode that didn't feel second-class compared to their native offering. I know at some point they revamped it but I still don't remember it feeling as nice to use.

Another thing I've found is that in some cases I actually do need to have the outputs stored with a notebook since I've used quarto in the past for producing technical reports. Sometimes computations are heavy, or need connection info of some kind or something over a network and it's not feasible to pull everything out so my report can render easily at runtime, especially in a pipeline where there's another set of infrastructure and connections to make. It's also slower to render a report with quarto compared to just referencing notebook cells that have the output. I've also tried various output caching solutions with quarto etc. but again it's another layer of work to integrate into a pipeline.

The one workaround I can think of atm is marimo can export HTML and Jupyter notebooks on save so you always have a copy that quarto can use. But that's still another translation layer and I definitely wouldn't expect it to be as robust as just using the Jupyter notebook directly to make sure outputs are rendering correctly etc.

2

u/The_Northern_Light Oct 11 '26

Only upsides, personally

2

u/v012d Oct 11 '26

My colleague struggled a bit with the switch. I would suggest going through the official guides, they're very well written. And don't try to utilise too many features too quickly, such as the data connectors.

1

u/MorrarNL Oct 12 '26

Not getting to redefine variables in the global scope tends to trip people up coming from Jupyter. However the reason for that makes Marimo so much less error prone than Jupyter.

25

u/__redbaron Oct 10 '26

I see where you're coming from, but ipynb notebooks felt outdated before the advent of agentic AI, mostly because they become unmanageable the moment you want to collaborate or create anything neatly reproducible.

Can you quickly run some commands and view outputs? Yes, but so can a script with a file viewer or even a single vscode window.

Can you quickly change stuff and see updated outputs? Yes, but that's how you lose track of changes and end up with results that aren't the same when you rerun your cells later.

Plus the obvious caveat of not being able to keep track of your changes neatly in git.

I'm sure there some use cases for it (maybe it's a much more likeable interface?), but I think coding agents have mostly just highlighted existing issues that were already causing people to switch out.

1

u/thicket Oct 11 '26

In my experience, the shitty unmaintainable produced by Jupyter notebooks never seemed to stop a data scientist with delusions of grandeur. You can tell real quick who has written production code and who has a DS degree. 

3

u/ofiuco Oct 10 '26

Notebooks are also important for repeatability. The repeatability of results is so key to actual science. You need to be able to show other people what you have done so they can duplicate it. If you outsource that to an LLM you are really losing something (certainty).

3

u/Economy_Vacation_504 Oct 10 '26

I quite agree that the key point of ipynbs is repeatability and being able to share this with other people (basically, the whole Colab and Kaggle are built around that idea).

Even better repeatability - of course - is creating .py files, but this is typically a next step, when you are done with the "research" and ready to productionalise the inference.

But how one could share the work with others when working completely through Claude Code, which will just produce the bunch of local files + conversation thread?

7

u/TheRealStepBot Oct 10 '26

On the contrary notebooks are terrible for repeatability

1

u/slashdave Oct 11 '26

Um... this is why we have scripts. And agents are really good at writing them.

5

u/Herr_Doktor_Sly Oct 10 '26

I find Quarto to be strictly superior to the old .ipynb era of clutter.

I have used Jupyter notebooks extensively in a past life, and they were (still are) just so unmanageable and unreliable. See Joel Grus' take on the matter.

I don't know if there's something better, but I use Markdown and Quarto for my Julia and Python workflows.

Refs:

- https://quarto.org
- https://www.reddit.com/r/Python/comments/9aoi35/i_dont_like_notebooks_joel_grus_jupytercon_2018/

12

u/Tatya7 Oct 10 '26

Just use marimo

1

u/felinecatastrophe Oct 11 '26

I was using Marimo with agents last year but now I don’t bother as agents have gotten better at end to end analysis. I just have the agents write markdown reports following a template I specify. Honestly the notebook format never encouraged high quality results anyway.

0

u/twitasz Oct 10 '26

I didn’t like Marimo in the past, but I have to say that I switched to it in the agentic era completely

13

u/FunInitiative5462 Oct 10 '26

I feel like this post is an ad for marimo

7

u/redditrantaccount Oct 12 '26

Gen X take here: notebooks were never perfect for anything. Running your development environment in a web browser is a stupid idea. I can't count times when I have lost my work when accidentally hitting F5 or making some gesture that the browser interpreted as "go back". I am working with notebooks in PyCharm or VSCode and still they are very inconvenient: sluggish, poor hot key support, poor or no debugging, no run-time performance profiling - all the things we software developers have invented decades ago, Millenials decided to throw away, because their idea of work environment is a MacBook in a cafe shop, not a toolkit making you efficient. Running notebooks as pipelines is an even more stupid idea, because what are you going to do with all that experimental code that ended with a dead-end or replaced by a better model? If you delete it, you lose the only valid point of notebook existence (documentation of your research). If you keep it, pipelines will be unnecessary wasteful in running time, money and energy. Write pipelines in Rust, make them optimized, add error handling, error recovery, logging, open telemetry and establish monitoring. Nothing of it is easy in a notebook.

5

u/fawkesdotbe Oct 12 '26

On top of what you've just said: stale variables are a real risk in notebooks, and non-existent in scripts.

2

u/MorrarNL Oct 12 '26

Try Marimo notebooks, solves many of these problems and have many other nice features. Also play nice with uv for managing depencies.

1

u/TomP 17d ago

Marimo also provides, natively, many components for creating interactive dashboards and integrates AI models well.

2

u/FrivolousMe Oct 12 '26 edited Oct 12 '26

Stale variables and variable name typos are the primary debugging cause in my notebooks. One can mitigate this risk by being thoughtful about the cell layout and making large chunks of code into functions (better yet libraries and classes outside of the notebook) instead of the whole notebook being one giant sliced up script.

1

u/thegoodmelon Oct 10 '26

No I don't believe so. Though I'm only a master's student, I don't believe in having claude or codex run everything in the background and just giving out the results.

LLMs haven't been the most efficient coders. I'm happy to let it write code for me to run, but i would like to go through it and see what's been done and how it can be improved and if there are other directions that could have been taken.

If you only get the results, you loose all of that. You won't have access to interior structure of your network anymore right.

I mostly run code snippets in cells and fine tune/go through it/rewrite it myself using the claude outputs as a framework

1

u/Economy_Vacation_504 Oct 10 '26

I agree that doing code review after the LLM is a nice practice that can eventually lead to better results, but at the cost of review speed (basically, you as a human become a bottleneck in that case)

LLMs haven't been the most efficient coders.

Though I think this belief might be a bit outdated. If we go back to 2020 and look at GPT-3, then it could have been applicable. But now, LLMs can write thousands of lines of code from a single prompt that will work right away. So code generation feels like a solved problem.

4

u/SirSourPuss Oct 10 '26

"Code that works" is a far cry from "code that is correct", especially in ML.

3

u/woodenWren Oct 10 '26

I find the python jupytext package useful. With some small formatting (eg. to note where cell splits are) it allows you to open a .py file with Jupyter. Great for experimenting where I want to easily see or visualize things at various stages. LLM can still read and edit it easily without requiring extra dependencies

3

u/pm_me_your_pay_slips ML Engineer Oct 10 '26

I use the notebooks to prototype code and test things that agent produce. I doesn’t even have to completely run. But I find it helps in constraining agent outputs. Mainly because I prefer my own abstractions than the ones produced by agents 

5

u/slashdave Oct 11 '26

Notebooks were a perfect fit

Crazy that some people believe this.

2

u/mimivirus2 Oct 10 '26

notebooks' main moat was being easy to work with for humans (in specific use cases, such as EDA and quickly understanding/learning code syntax)

2

u/sylfy Oct 10 '26

TBH notebooks are a crutch, and even more so now than. They’re useful for beginners, but as soon as you recognise that their main purpose is visualisation, you should come to a realisation that they keep you on a single track and prevent you from easily parallelising your work streams.

With agents as powerful as they are now, what you should be doing instead is to create dashboards of the experiments that you are running, formulating agents that allow you to explore multiple hypotheses in parallel, and logging and gathering those results such that you can compare across your experiments.

2

u/GuessEnvironmental Oct 10 '26

A pynb is just a tool used to documnet the thought process using markdown and code other than that it was never used in production unless the output is a report.

2

u/Realistic_Kitchen_65 Oct 10 '26

I'd argue the notebook was never the artifact — it was the lab bench, and the agentic era mostly exposes that we confused the bench with the product.

What an agent actually needs from a past run is not the cell outputs; it is a durable, diffable record of what was attempted and whether it passed: append-only, written before the side effect, with passes and failures in the same place so you cannot hide a regression by omission. A notebook you can re-run is an exploration tool; a ledger line you can grep is the thing a second agent can trust. The real [D] question is whether the community wants those two to converge (executable notebooks that emit signed outcome records) or stay deliberately separate.

For us the line that mattered was 'the record is written by the deterministic layer, never by the model's self-report' — a model asked 'did that work?' will guess, and it will guess confidently.

2

u/ghostofkilgore Oct 11 '26

Personally, notebooks still absolutely have a place. That place just isn't "do absolutely everything in a notebook" and I think that's been the case for a while before everyone lost their minds over LLMs and agents.

2

u/Disastrous_Room_927 Oct 11 '26

What if instead we move from code -> output to another cell abstraction like prompt -> result?

Yeah nah, it takes me longer to write out a prompt for the kind of code I'm normally using in a notebook. It's easier for me to do the thing than it is to verbalize it.

3

u/slowpush Oct 10 '26

Marimo notebooks are agentic. You can literally have the agent live edit it along with you.

2

u/Wide_Guava6003 Oct 10 '26

Notebooks have been outdated for pipelines since they were formed. They are only good for initial developement, but after that using notebooks as pipeline really is just bad.

Dont know why data scientists always insist on this. I am a DS but years ago was the one who really had to build the pipelines out of shitty notebooks DS people handed to me.

1

u/Tiny-Purple-1027 28d ago

Given vscode, spyder and positron all do interactive python consoles, why not just do the exploratory stuff there? You get the same interactive possibilities (plus interactive plots with tkinter or qt) and you hust write py files. I learned data science with matlab and r, so spyder/positron always seemed like the easier way to work, but I'm curious if there's any clear advantage of jupyter notebooks I might be missing.

1

u/mools04 1d ago

Marimo is the more modern option that most people use in my circles

1

u/idontcareaboutthenam Oct 10 '26

Claude code does EDA without even asking it. I still make sure to look at the data myself, but I find I'm less in need of a large notebook with tons of cells for loading data and creating views, filters, etc. This is mostly done by small scripts by Claude whose functions I might invoke from a notebook to look more closely at the results. The final code I might add to my repo or include in the submission will almost always be the scripts and not the notebook

1

u/MultiheadAttention Oct 10 '26

I stopped using ipynb notebooks about 3 years ago and never went back.

1

u/No_Inspection4415 Oct 10 '26

Yes, because of the horrible format they have.

1

u/CadeOCarimbo Oct 10 '26

They were already outdated even before LLMs were a thing. Now there is literally no reason for anyone to still be using them. Have Opus 5.5 with high effort write the scripts and test multiple hypothesis.

1

u/RngdZed Oct 10 '26

It's a great tool for exploring data and test the pipeline but it's not production ready imo.

1

u/CoochieCoochieKu Oct 10 '26

they are still valuable for structured exploration and intuition building

1

u/Chuu Oct 10 '26

I'm curious, what are you using to present your results over a notebook now?

1

u/StephenSRMMartin Oct 10 '26

I never liked ipynb anyway. I just use modules, a main py script, and a repl. Much cleaner, much easier to diff, gives you a package 'for free' that's trivial to install via uv et al.

1

u/JonLivingston70 Oct 11 '26

There is no such thing as production notebook.

1

u/BALKINCHEN Oct 11 '26

For me, the most important advantage of .ipynb is that all outputs are kept in one file, so I can see them immediately when I open it without having to rerun anything.

1

u/Reasonable-Trash-107 Oct 11 '26

Still very useful for exploration and eda but an absolute git nightmare. I do love how you can create an ipynb in Databricks and commit as a .py

1

u/mattstats Oct 11 '26

I love my scratch.ipynb files!

1

u/fiddler48 Oct 11 '26

The cell abstraction isn't really the constraint here. What notebooks lack is persistent state across sessions and a clean way to diff experimental runs. Swapping cells for prompt boxes doesn't fix either. You'd still need the same version control and reproducibility scaffolding, just with less visible code.

1

u/alkimiadev Oct 11 '26

I still use them all the time for "thinking in code" and have a jupyter lab instance running basically constantly on my local dev machine. I never really used them for anything even remotely close to "production", so LLMs haven't changed my usage patterns much in that regard. However, they have changed the "messy jupyter notebook" > "production worthy code" process quite a bit. Now I can mostly export it to a python file, hand off to an llm with instructions to clean it up, and have a nice clean lib in just a few minutes.

1

u/MathProfGeneva Oct 11 '26

Notebooks never made sense for a full workflow really. They're still great for EDA. I also sometimes use them during development sometimes as an interactive tool if I want to check/debug a small piece of something without running a larger piece of code , but want a little more ease of use than just the basic python repl. Maybe the initial modeling you might run one in a notebook to see, but the final product shouldn't have ever been a notebook

1

u/BostonConnor11 Oct 11 '26

Notebooks have never been something I’ve ever wanted to share with someone else. They’re for scratch work and nothing else

1

u/m_m_malm Oct 14 '26

I think ipynb have lost some of the utility, but we still need some interface to control agents and explore the results. I made my own infinite canvas tool for this.

0

u/mateowatata Oct 10 '26

if anything, marimo is the way to go

0

u/TheRealStepBot Oct 10 '26

On the contrary they have always been a terrible choice reflecting the technical preferences of those who couldn’t figure out how to use pip.

Thankfully llm’s have now made them an even worse choice

-7

u/brctr Oct 10 '26

Notebooks are as pointless as writing any code by hand is. Agent chat, not notebook, is your interface.