• by killjoywashere on 3/4/2019, 11:22:35 AM

    An acquaintance once advised me to keep a context file: all the little "notes to self", code snippets, key config elements, etc, in a file. I've tried a few times in Vim but finally really got traction in Jupyter, through a combination of my org's massive Windows dependencies, which is definitely not the Jupyter community'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'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.

    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.

  • by fulafel on 3/4/2019, 4:28:53 AM

    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?

  • by qd6pwu4 on 3/4/2019, 2:57:48 AM

    It seems to be a nice introduction to numpy, pandas, and matplotlib

  • by quotz on 3/3/2019, 9:23:15 PM

    Any reviews on this ?

  • by pooya13 on 3/3/2019, 10:53:08 PM

    When an open source book has 150 open PRs and the last commit is from 4 months ago I am discouraged to spend time on it.

  • by nicholast on 3/4/2019, 1:03:14 AM

    I also recommend checking out the open source Automunge tool for automated data wrangling at automunge.com