Author says Claude now one-shots distributed systems bugs that used to take him two days but most top comments here are still playing down frontier model capabilities.
Are we collectively in denial? It's understandable as the craft as we knew it is being disrupted by tools that have improved at an astonishing pace.
I find OpenAI's speech-to-text model the best of the lot. It can handle my & my 5-year old daughter's Indian accent pretty well.
I wonder if they run the STT model's output through the current model (that we're chatting with) as a final pass - since the text seem to be well aligned to the current conversation context.
For long prompts, I often speak to OAI web/app and copy-paste the text to Claude / Gemini :)
Really cool. If somebody doesn't want to adopt a new platform, take a look at open source Jupyter MCP Server[1]. Once integrated with Claude, it can execute code on the live notebook kernel.
I just let Claude write notebooks, run top to bottom, debug & fix errors & only ping me when everything is working.
Thanks for sharing! MLJAR Studio was created for people with domain knowledge but not much technical expertise. For them, setting up a Python environment, installing required packages, configuring Jupyter Lab, the MCP server, and Claude Code might be technically demanding.
MLJAR Studio is a desktop application available for Windows, MacOS, and Linux. MLJAR Studio creates a Python environment for the user and installs all required packages. The user can focus on data rather than fighting technical challenges.
Unfortunately some of us use Instagram specifically to keep in touch with people (IG DMs). and Meta does not seem to want to split off the messaging from the main app the same way they did with FB messenger for some reason (I would love it if they did). For Twitter, some of us need it for work as well (lots of interesting AI research published directly to Twitter). Reddit is definitely pure entertainment yeah. But there are nuances.
Twitter, I uninstalled the app and used via the browser for about a year until I finally gave it the boot outright.
Similarly, I felt I needed it to “keep in touch” with people, but I ultimately decided the psychic tax was too high to maintain some lukewarm friendships when I have perfectly good ones in meatspace.
This was a huge one for me. Remember spending so much time posting and reading twitter and insta feeds when I was in car with my wife. Totally different now. We talk and converse about what's going on with our kids, stuff at work, its way better. We both feel much more connected.
I also turned off all notifications from all my apps, period end of story. My battery lasts for days and its not completely distracting. Made a huge difference in my ability to focus.
When you have executable code in the documentation, folks want to follow PR-review workflow with the docs as well - which is a bit more team investment than editing a wiki.
Is anyone here worried about pouring hot water into Aeropress plastic? I know it's polypropylene, which is BPA-Free but could there be things that we haven't properly researched yet?
If you want to avoid plastic, Hario Switch is a great alternative. It allows you to steep and release, kinda similar to AeroPress (pressure only comes from gravity though).
Cone is made of glass, stopper is from stainless steel, but the base is made of silicone. I imagine the hot water contact with the silicone will be a lot less compared to AeroPress.
If you get the size 03, you can more easily brew enough coffee for 2 people.
Heating plastics can release not just BPA but also phthalates, dioxins, and other harmful compounds which are linked to lots of nasty heath issues like hormone disruption, cancer and reproductive problems.
Polypropylene is generally considered one of the safer plastics with it's high heat tolerance meaning doesn't leach harmful chemicals. While pure polypropylene may be considered safe, additives used in the manufacturing such as colourants or fillers could have their own health risks.
Personally avoid mixing food or drinks with any heated plastics, including my coffee. I use French press for my coffee but if Aeropress is your thing and want to avoid plastic I've heard good things about the Cafelat Robot which is made almost entirely out of aluminium and stainless steel.
We all know .ipynb JSON format is not a great fit for Git. The Jupyter ecosystem has come a long way in the last few years. Solving this really comes down to a few tools -
- JupyterLab Git Extension[1] for local diffs (pre-commit diffs)
- nbdime[2] / nbdev[3] for resolving .ipynb git merge conflicts
- GitHub PR code reviews with ReviewNB[4]
- Alternatively, if you don't care about cell outputs then Jupytext[5] to sync .ipynb JSON to markdown
Disclaimer: I built ReviewNB. It's a completely bootstrapped business, 5 years in the making and now used by leading DS teams at Meta, AWS, NASA JPL, AirBnB, Lyft, Affirm, AMD, Microsoft & more[6] for Jupyter Notebook code reviews on GitHub / Bitbucket.
> Alternatively, if you don't care about cell outputs then Jupytext[5] to sync .ipynb JSON to markdown
Notice that using markdown is a possibility for jupytext, but not the only one. More interestingly, you can also store your notebooks as plain python files, whose comments are interpreted as the markdown cells of the notebook.
This is very useful, and not only for version control: if your notebooks are python files they can be executed easily in CI or by third parties just by launching the interpreter. No need even of the jupyterlab dependency.
With some care, you can craft a single python file "foo.py" that can be used at the same time as
1. an executable command-line program (that happens to be written in python)
2. an importable python module
3. a jupyter notebook (to open it you need the jupytext extension of jupyter)
4. the documentation with auto-generated figures, convertible to html or to pdf using "jupyter nbconvert --execute"
5. a regular .ipynb if for some reason you want to distribute the outputs in a re-executable format
For small simple projects, to showcase, describe and illustrate an independent algorithm, we have found this structure invaluable.
This is a post from my Linkedin page on my hopes for Jupyter notebooks and git. Anyone know of progress along this line?
#Jupyter notebook and git
As much as Jupyter Notebooks have been a great tool for data science, the transition to deployment, and the general software engineering friendliness of Jupyter Notebooks could use some work. From time to time, I have explored how others have dealt with turning notebooks into an organized codebase and outputs. To date, I have not found a comfortable approach for me. The ideal approach for me would be to use something like 'node metadata' in the way of [Leo Editor](https://leo-editor.github.io/leo-editor/) to function as 'decorators' for a notebook cell for integration with git.
By this I mean using something like special markers in Python comments (since much of data science is done with Python) to map the content of a cell (or output) to a git repository. Better yet, define a special cell type for git metadata preceding a code cell. Then implement some basic git operations on the contents of a cell. Let's suppose we use @@git as a marker for metadata in comments for git.
--- beginning of cell ---
# @@git %upstream%=https://github.com/pyro-ppl/pyro
# @@git %local%=~/repo/pyrodev
# @@git %branch%=burnburnburn
# @@git %file%=examples/cvae/util.py
# Here begins the contents of the util.py file
...
--- end of cell ---
An extension would implement items in the menubar for various git operations:
stage - stage the content as util.py file
checkout - checkout from upstream, replace local copy, and refresh content of cell
commit - commit stage file specified by %file%
status - ...
Imagined workflow is that once a working idea scattered throughout a notebook has been sketched out, the user would mark the notebook cells that should be mapped to files in a git repository. Also this could be used in a mixed dev/data science environment where library code under development can be pulled right into a notebook.
Yes, there will be problems with committing code with comments that are specific to one user which is why a special cell type makes sense. Yes, there will be problems that I can't even imagine right now but ...
Please message me if you know of a cell-based git extension for Jupyter Notebooks.
reply