<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>killjoywashere</author><text>An acquaintance once advised me to keep a context file: all the little &amp;quot;notes to self&amp;quot;, code snippets, key config elements, etc, in a file. I&amp;#x27;ve tried a few times in Vim but finally really got traction in Jupyter, through a combination of my org&amp;#x27;s massive Windows dependencies, which is definitely not the Jupyter community&amp;#x27;s default (needed to document lots of little idiosyncrasies), and actually having interesting data in that world. What I really like about Jupyter for this is that it&amp;#x27;s trivial to mix it all together: a link to a handbook like this, how to decode and encode Windows environment variables, tips on Vim, python, pandas, plotting, etc.&lt;p&gt;And I was really struck how a number of the headings in this handbook mapped exactly to the headings in my context file. I suspect this will not be the last time I click that link.</text><parent_chain></parent_chain></comment><story><title>Python Data Science Handbook: Full Text in Jupyter Notebooks</title><url>https://github.com/jakevdp/PythonDataScienceHandbook</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>fulafel</author><text>Is there a way to run notebooks automatically, so you could regenerate notebooks like this after some library code changes or dependency upgrades and check that everything stillw orks?</text><parent_chain></parent_chain></comment><story><title>Python Data Science Handbook: Full Text in Jupyter Notebooks</title><url>https://github.com/jakevdp/PythonDataScienceHandbook</url></story>