Summary
Creating well designed software is largely a problem of context and understanding. The majority of programming environments rely on documentation, tests, and code being logically separated despite being contextually linked. In order to weave all of these concerns together there have been many efforts to create a literate programming environment. In this episode Jeremy Howard of fast.ai fame and Hamel Husain of GitHub share the work they have done on nbdev. The explain how it allows you to weave together documentation, code, and tests in the same context so that it is more natural to explore and build understanding when working on a project. It is built on top of the Jupyter environment, allowing you to take advantage of the other great elements of that ecosystem, and it provides a number of excellent out of the box features to reduce the friction in adopting good project hygiene, including continuous integration and well designed documentation sites. Regardless of whether you have been programming for 5 days, 5 years, or 5 decades you should take a look at nbdev to experience a different way of looking at your code.
Interview
- Introductions
- How did you get introduced to Python?
- Can you start by describing what nbdev is and the goals of the project?
- What is the story behind how and why it got started?
- Who is the target audience for the nbdev project?
- How does that focus influence the features and design of nbdev?
- What do you see as the primary challenges of building and collaborating on projects written in notebooks?
- What are some of the other projects that are working to simplify or improve the experience of using notebooks?
- How does nbdev compare to or complement those other tools?
- Can you describe how nbdev is implemented?
- How has the design and goals of the project evolved since it was first started?
- What is the workflow of someone who is using nbdev?
- At what point in the lifecycle of a notebook oriented project should someone start integrating nbdev?
- How does nbdev scale when working on a project that spans multiple notebooks/modules?
- How does working in a notebook environment change your approach to software development and project design?
- What are the most interesting, innovative, or unexpected ways that you have seen nbdev used?
- What are the most interesting, unexpected, or challenging lessons that you have learned from working on nbdev?
- When is nbdev the wrong choice?
- What do you have planned for the future of the project?
This article has been published from the source link without modifications to the text. Only the headline has been changed.
