Untitled13.ipynb
summary
Shows a practical rethinking of notebooks: code cells become reactive DAG nodes with immutable globals, updates propagate automatically, and deletion triggers errors rather than silent desyncs. Demos actually build: a draw-data anywidget that auto-installs deps via uv, returns a Polars dataframe, links to DuckDB/SQL cells, generates Altair charts that select subsets, hooks to LLMs (OpenRouter / Cloud Code) for SQL or Python, exports to a runnable Python file, runs as an app, and the widgets and gamepad annotation pipeline work end to end.
AI-written summary · about
chapters (15)
- 0:00Welcome
- 1:11Jupyter notebooks limits
- 3:35Marimo notebooks intro
- 8:52Reactive UI widgets
- 12:01AnyWidget libraries
- 17:36Code and data in Marimo
- 20:49SQL in Marimo
- 23:13Data sources in Marimo
- 28:25JSON export in Marimo
- 31:13Notebooks to CLI apps
- 34:04Unit testing in Marimo
- 38:56Reusable functions
- 41:46Interactive Python dreams
- 43:29Advanced demos
- 45:15Closing and Q&A
related talks
36mReactive Notebooks for Python
27mThe Future of Notebooks in a Claude Code World
34mCode the Docs: Interactive Document Environments
34mReactive Notebooks for Python
01h 29mTurning Jupyter Notebooks into Data Applications
34mReadme.md? We Can Do Better
01h 16mMake your research interactive with Jupyter Dashboards
29mUsing Jupyter notebooks to develop and share interactive data displays
