# nbdev

nbdev is a notebook-driven development platform for creating software with Jupyter Notebooks, including documentation, testing, continuous integration, and packaging.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Why I Stopped Using nbdev

DevFeed: [Why I Stopped Using nbdev](<https://devfeed.tech/articles/why-i-stopped-using-nbdev-18783.md>)

Original publisher: [Read original article](<https://hamel.dev/blog/posts/ai-stack/>)

Author: Hamel Husain

Published: 2026-01-18T08:00:00Z

Content type: opinion

Language: en

Sources: [Hamel Husain](<https://devfeed.tech/sources/hamel-husain.md>)

Topics: [nbdev](<https://devfeed.tech/topics/nbdev.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [jupyter](<https://devfeed.tech/topics/jupyter.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [clean-code](<https://devfeed.tech/tags/clean-code.md>), [code-documentation](<https://devfeed.tech/tags/code-documentation.md>), [development](<https://devfeed.tech/tags/development.md>), [development-environment](<https://devfeed.tech/tags/development-environment.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [jupyter-notebooks](<https://devfeed.tech/tags/jupyter-notebooks.md>), [nbdev](<https://devfeed.tech/tags/nbdev.md>), [python](<https://devfeed.tech/tags/python.md>), [solve](<https://devfeed.tech/tags/solve.md>), [thinking](<https://devfeed.tech/tags/thinking.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

The author stopped using nbdev because its notebook-centered workflow now clashes with AI coding tools, which are better suited to conventional source code and may confuse notebook edits with the generated Python library. nbdev's single source of truth combines code, documentation and tests in Jupyter notebooks, then transpiles them into a library and website. The author also found that this arrangement did not ensure documentation was sufficiently thorough: good documentation still takes effort. They say AI can now explain undocumented codebases and help maintain separate documentation, making co-located code and docs less compelling. The excerpt also argues that careful thinking and clean code depend on developer discipline, not on notebooks or AI tools. The supplied text cuts off during the collaboration and adoption section, so it does not establish the author's full account.

### Source excerpt

Programmers love to proclaim they've found the best tool. Paul Graham called Lisp his "secret weapon." DHH described Ruby as "a magical glove that just fit my brain perfectly." Pieter Levels ships million-dollar products with vanilla PHP and jQuery. These declarations aren't about the languages themselves. They're about developers finding tools that fit how they think. When the environment clicks, you move fast. I had that experience with nbdev, a development environment for literate programming that I helped build and maintain1. I created hundreds of projects with it and was one of its biggest proponents. Today, I no longer use it. AI coding tools changed the trade-offs. Fighting the AI The beauty of nbdev is its workflow. You write code, documentation and tests in one source of truth: Jupyter notebooks. Afterwards, these notebooks are transpiled into a Python library and documentation website. This workflow is idiosyncratic. AI coding tools, trained on vast amounts of conventional source code, get confused. They struggle to differentiate between editing the notebook and editing the final source code. It feels like fighting the AI instead of working with it. I write software to solve problems, not to write code. I want to work in an environment where AI has the highest chance of success. With nbdev, I was swimming upstream. Some argue that AI tools encourage lazy thinking: that without guardrails, developers skip the hard work of breaking problems into steps. But thinking step-by-step is a human skill. Notebooks don't force you to write clean code. AI tools don't force you to think carefully. Discipline comes from the developer, not the environment. Tools Don't Matter As Much As I Thought A central promise of literate programming is better documentation. By keeping code and docs in one place, you reduce the chance they become stale. Strangely, many nbdev projects lacked sufficient documentation for my taste. Sometimes, this helped me learn a codebase by contributin

## Nbdev: A literate programming environment that democratizes software engineering best practices

DevFeed: [Nbdev: A literate programming environment that democratizes software engineering best practices](<https://devfeed.tech/articles/nbdev-a-literate-programming-environment-that-democratizes-software-engineering-best-practices-68702.md>)

Original publisher: [Read original article](<https://github.blog/developer-skills/programming-languages-and-frameworks/nbdev-a-literate-programming-environment-that-democratizes-software-engineering-best-practices/>)

Author: Hamel Husain

Published: 2020-11-20T17:00:15Z

Content type: article

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [nbdev](<https://devfeed.tech/topics/nbdev.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [builds](<https://devfeed.tech/tags/builds.md>), [code-navigation](<https://devfeed.tech/tags/code-navigation.md>), [codespaces](<https://devfeed.tech/tags/codespaces.md>), [conda](<https://devfeed.tech/tags/conda.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [developer-skills](<https://devfeed.tech/tags/developer-skills.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [engineering-best-practices](<https://devfeed.tech/tags/engineering-best-practices.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [nbdev](<https://devfeed.tech/tags/nbdev.md>), [programming](<https://devfeed.tech/tags/programming.md>), [programming-languages-frameworks](<https://devfeed.tech/tags/programming-languages-frameworks.md>), [python](<https://devfeed.tech/tags/python.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

nbdev is a Python literate programming environment built on Jupyter notebooks. It integrates documentation generation, unit testing, continuous integration through GitHub Actions, notebook and source code synchronization, conflict resolution, and package publishing to reduce friction in software engineering workflows.

### Source excerpt

Learn about nbdev, a new literate programming environment for Python.