\n",
"{img(im, link=True)}\n",
"\n",
"# {nm}\n",
"\n",
"## {detl}\n",
"\n",
"### {txt}\n",
"
\n",
"\"\"\"\n",
"\n",
"testms = '\\n'.join([\n",
" testm('chris-lattner.png', 'Chris Lattner', 'Inventor of Swift and LLVM',\n",
" 'I really do think [nbdev] is a huge step forward for programming environments.'),\n",
" testm('fernando-pérez.jpeg', 'Fernando Pérez', 'Creator of Jupyter',\n",
" '[nbdev] should be celebrated and used a lot more — I have kept a tab with your original nbdev blog post open for months in Chrome because of how often I refer to it and point others to this work.'),\n",
" testm('david-berg.jpeg', 'David Berg', 'Software Engineer, Netflix',\n",
" 'Prior to using nbdev, documentation was the most cumbersome aspect of our software development process… Using nbdev allows us to spend more time creating rich prose around the many code snippets guaranteeing the whole experience is robust.\n",
"\n",
"
\n",
"
\n",
"\n",
"# Chris Lattner\n",
"\n",
"## Inventor of Swift and LLVM\n",
"\n",
"### I really do think [nbdev] is a huge step forward for programming environments.\n",
"
\n",
"\n",
"
\n",
"
\n",
"\n",
"# Fernando Pérez\n",
"\n",
"## Creator of Jupyter\n",
"\n",
"### [nbdev] should be celebrated and used a lot more — I have kept a tab with your original nbdev blog post open for months in Chrome because of how often I refer to it and point others to this work.\n",
"
\n",
"\n",
"
\n",
"
\n",
"\n",
"# David Berg\n",
"\n",
"## Software Engineer, Netflix\n",
"\n",
"### Prior to using nbdev, documentation was the most cumbersome aspect of our software development process… Using nbdev allows us to spend more time creating rich prose around the many code snippets guaranteeing the whole experience is robust.
nbdev has turned what was once a chore into a natural extension of the notebook-based testing we were already doing.\n",
"
\n",
"\n",
"
\n",
"
\n",
"\n",
"# Erik Gaasedelen\n",
"\n",
"## Software Engineer, Lyft\n",
"\n",
"### I use this in production at my company. It’s an awesome tool… nbdev streamlines everything so I can write docs, tests, and code all in one place… The packaging is also really well thought out.
From my point of view it is close to a Pareto improvement over traditional Python library development.\n",
"
\n",
"\n",
"
\n",
"
\n",
"\n",
"# Roxanna Pourzand\n",
"\n",
"## Product Manager, Transform\n",
"\n",
"### We’re so excited about using nbdev. Our product is technical so our resulting documentation includes a lot of code-based examples. Before nbdev, we had no way of maintaining our code examples and ensuring that it was up-to-date for both command inputs and outputs. It was all manual. With nbdev, we now have this under control in a sustainable way. Since we’ve deployed these docs, we also had a situation where we were able to identify a bug in one of our interfaces, which we found by seeing the error that was output in the documentation.\n",
"
\n",
"\n",
"
\n",
"
\n",
"\n",
"# Hugo Bowne-Anderson\n",
"\n",
"## Head of Developer Relations, Outerbounds\n",
"\n",
"### Nbdev has transformed the way we write documentation. Gone are the days of worrying about broken code examples when our API changes or due to human errors associated with copying & pasting code into markdown files. The authoring experience of nbdev is also powerful, allowing us to write prose and live code in a unified interface, which allows more experimentation with technical content. On top of this, nbdev allows us to include unit tests in our documentation which mitigates the burden of maintaining the docs over time.\n",
"
\n",
"\n",
"\n",
"
\n"
],
"text/plain": [
"