Top all-time · #10020
R
ReviewNB
Company blog · reviewnb.comprogrammingai
ReviewNB is the company blog at reviewnb.com, writing about programming and ai. Since 2018, 8 different Hacker News readers have linked it 29 times, most often “Show HN: ReviewNB – Jupyter Notebook Diffs for GitHub”. No feed was found, so read it on the site itself.
No feed foundVisit the blog
29mentions?
8HN people?
2018–2026first – last linked?
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link ReviewNB, a code review tool for Jupyter notebooks on GitHub. One commenter recommends it as a diff tool for notebooks.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
11,000+ GitHub installs. Trusted by teams at Apple, Airbnb, Spotify, NASA JPL. Review notebook PRs with rich diffs, rendered outputs, and cell-level comments.
Most-linked posts?
- Show HN: ReviewNB – Jupyter Notebook Diffs for GitHub6 people · 16 mentions · first linked 2018-11-20
- Git and Jupyter Notebooks Guide2 people · 2 mentions · first linked 2023-06-30
What Hacker News says?
If you are in need of a diff tool for jupter notebooks use https://www.reviewnb.com/ and for word documents use https://www.simuldocs.com/
Comment linking /
on “Difftastic, a structural diff tool that understands syntax”Submitted Show HN: ReviewNB – Jupyter Notebook Diffs for GitHub as a story · 4 points
HN discussion> don’t play well with git I agree, and this is why I built - - ReviewNB - Code review tool for Jupyter notebooks(think rich diffs and commenting on notebook cells) - GitPlus - A JupyterLab extension to push commits & create GitHub pull requests from JupyterLab. [1] https://www.reviewnb.com/ [2] https://github.com/ReviewNB/jupyterlab-gitplus
Comment linking /
on “Swift: Google’s Bet on Differentiable Programming”Submitted Visual Diff and Commenting for Notebooks as a story · 3 points
HN discussionVersion control for Jupyter notebooks was one of the biggest complaint I had. Specifically, diff and merge with the JSON files (.ipynb) is ugly. I built ReviewNb[1] to solve one of those problems (diff). Note that, there is nbdime[2] which works well for local diff/merge. The idea for ReviewNb is to have much tighter integration with GitHub etc. [1] https://reviewnb.com [2] https://nbdime.readthedocs.io/en/latest/
Comment linking /
on “Why Jupyter is data scientists’ computational notebook of choice”Submitted Git and Jupyter Notebooks Guide as a story · 2 points
HN discussionEx-Amazon engineer here. Worked for ~4 years in the Prime Music team. Contrary to popular belief, I had incredible time at Amazon. Learned a lot, good work life balance, progressed to L5 etc. Primary reason I quit is to start something of my own and not live under a draconian H1-B visa that treats people like second class citizens (will save H1-B rant for some other time). What am I doing now? I enjoy building dev t…
Comment linking /
on “Ask HN: Ex-FAANG developers, where are you now and why?”Submitted ReviewNB: Code Reviews for Jupyter Notebooks as a story · 2 points
HN discussionI built ReviewNB [1] to see visual diff for Jupyter Notebook changes & do a code review on it (by writing comments on cell changes etc.). One of the next feature for ReviewNB is a CI pipeline for Jupyter Notebooks on GitHub. The idea is to make it easy for users to specify notebook "tests"/"checks" that can then be run on every change. Given the nature of Notebooks, it's a bit hard to design CI for it in a clean way…
Comment linking /
on “Python Data Science Handbook: Full Text in Jupyter Notebooks”Submitted Claude Code with Jupyter Notebooks via MCP as a story · 1 points
HN discussion> The only build-in problem with Jupyter Notebooks is JSON, mixing input and output (and making it pain to work with version control) Absolutely. JSON notebook format makes it very hard to do code reviews, merge in remote changes etc. After being frustrated with lack of solutions, I built ReviewNB[1] specifically to do notebook code reviews on GitHub. Alternatively, Nbdime[2] is also a nice open source library to se…
Comment linking /
on “What’s wrong with computational notebooks?”Submitted Claude Code + Jupyter Notebooks Finally Work Well as a story · 1 points
HN discussion> Notebooks as we know them today have many pain points (versioning, reproducibility, collaboration) Absolutely. We're solving a small part of this by making notebooks play nicely with GitHub ( https://reviewnb.com ). Code reviews & collaboration for Jupyter Notebooks, essentially. Happy to see more products taking a stab at this problem. I'd be curious to know how you implement version control (git or something els…
Comment linking /
on “Launch HN: Deepnote (YC S19) – A better data science notebook”Submitted Git and Jupyter Notebooks: The Ultimate Guide as a story · 1 points
HN discussionJust checked out live commenting feature on Observable [1], the ability to send code suggestions and preview + merge suggestion with 1-click looks amazing. I built a tool [2] for Jupyter notebook code reviews which has commenting feature for GitHub pull requests (regular text comments). It would be great to have actual code edits/suggestions as review comments. [1] https://observablehq.com/@observablehq/suggestions-…
Comment linking /
on “Observable’s Not JavaScript”I understand the benefits of keeping front-end separate from back-end. - Separate teams working on front-end and back-end independently - Front end bundle can be served fast and cheap via CDN (only the naive serve static files with gunicorn/uwsgi right?) - and much more Knowing all that, I chose to mix up VueJS with Django solely to optimise for speed in a single person company. Thanks to this setup, - Authenticatio…
Comment linking /
on “Responder: A familiar HTTP Service Framework”A year ago, I was frustrated (and surprised) to see one can't do code reviews with Jupyter Notebooks. GitHub diffs for notebooks JSON are super messy. I set out to build ReviewNB[1], code review tool for Jupyter Notebooks. Turns out a lot of other people had this exact problem. One can see visual diffs & write review comments on notebook cell. Currently only works with GitHub though. If you want to diff locally (bef…
Comment linking /
on “Making Git and Jupyter Notebooks play nice”Two projects I've been watching with interest are https://kyso.io/for-teams and http://reviewnb.com .
Comment linking /
on “Show HN: A tool to convert Jupyter notebooks to beautiful blogs”It's not focused on collaboration, but it does add some critical pieces that otherwise make Jupyter development frustrating when working with a team. Specifically: `nbdev_prepare` ensures that diffs are as small as possible, by removing and standardising notebook metadata; and `nbdev_fix` fixes merge conflicts so that they are cell-level, rather than line level, so they can be opened and fixed in notebooks. Somethin…
Comment linking /
on “Nbdev: Create delightful software with Jupyter Notebooks”> thus making the diffs sane You can also use ReviewNB [1] that is literally built for Jupyter notebook diffs. You can see notebook visual diffs for any commit or pull request on GitHub. For pull requests, you can also write comments on a notebook cell (emulating the typical code review experience for Jupyter notebooks) Disclaimer: I built ReviewNB for Jupyter notebook code reviews on GitHub. [1] https://www.reviewn…
Comment linking /
on “Why we do machine learning engineering with YAML, not notebooks”Yes, nbdev can help with merge conflicts for notebooks [1]. Also checkout, - GitPlus[2] - JupyterLab extension for git version control - ReviewNB[3] - For notebooks diffs & commenting Disclaimer: I built GitPlus & ReviewNB [1] https://nbdev.fast.ai/#Avoiding-and-handling-git-conflicts [2] https://github.com/ReviewNB/jupyterlab-gitplus/ [3] https://www.reviewnb.com/
Comment linking /
on “Nbdev: Use Notebooks for Literate Programming”Converting notebooks to markdown is a fine idea (although you have to maintain both versions). I built ReviewNB ( https://www.reviewnb.com/ ) specifically to review Jupyter Notebooks on GitHub.
Comment linking /
on “Reviewing Zeppelin and Jupyter Notebooks”This works on Github: https://www.reviewnb.com/
Comment linking /
on “Reviewing Zeppelin and Jupyter Notebooks”I am working on Jupyter Notebook diff tool: https://reviewnb.com It's stimulating to write diff algorithms when textual diff is coupled with images, markdown, html, and code syntax rendering. Also, it's super useful for a lot of people in Data Science community.
Comment linking /
on “Ask HN: What are you working on and why is it cool?”Here are tools people commonly use for notebook version control with git - [1] nbdime to view local diffs & merge changes [2] jupytext for 2-way sync between notebook & markdown/scripts [3] JupyterLab git extension for git clone / pull / push & see visual diffs [4] Jupyerlab gitplus to create GitHub PRs from JupyterLab [5] ReviewNB for reviewing & diff'ing notebook PRs / Commits on GitHub Disclaimer: While I’m the a…
Comment linking /
on “Ask HN: Are there any good Diff tools for Jupyter Notebooks?”> hard to review code I built ReviewNB specifically for Jupyter notebook code reviews [1] > various kinds of tests for each of them Checkout treon, open source test framework for Jupyter Notebooks [2] Some other tips, - Move code into Python modules whenever possible - Maintain dockerfile / requirements.txt so your notebooks are easily reproducible - Setup treon in a CI/CD pipeline - Setup internal Binder [3] for qu…
Comment linking /
on “Ask HN: How do you organize, maintain and collaborate on Jupyter notebooks?”You bet. I built ReviewNB[1] specifically for Jupyter Notebook code reviews. There's also, - nbstripout[2] for stripping outputs automatically before every commit - nbdime[3] for diff'ing notebooks locally - jupytext[4] for converting notebooks to markdown and vice-a-versa [1] https://www.reviewnb.com/ [2] https://github.com/kynan/nbstripout [3] https://github.com/jupyter/nbdime [4] https://github.com/mwouts/jupytext
Comment linking /
on “Why is version control in Jupyter notebooks so hard?”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 sy…
Comment linking /
on “The Jupyter+Git problem is now solved”
