31–37 of 37 posts
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.
Last commit was 3 months ago, and there are 48 open pull requests ... Which one of us is accessing the wrong repo?
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 da…
Earlier quoted context omitted.
Even for leisurely reading, you expect an author to still be updating a book several years after it was published? What experience has led you to believe that's a reasonable expectation?
I don’t “expect” the authors to do anything. But I am not going to spend many hours of my time reading a book when I see that the book is not maintained because there are many great books on my backlog that ARE being maintained by the authors/community.
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 da…
hmm interesting idea. I've been trying all kinds of different tools for documenting my work/code snippets/notes.... But nothing sticked. Mind explaining more on that? Would it be stupid to have a wiki like system inside jupyter?
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 da…
hmm interesting idea. I've been trying all kinds of different tools for documenting my work/code snippets/notes.... But nothing sticked. Mind explaining more on that? Would it be stupid to have a wiki like system inside jupyter?
Disclaimer: I have used todoist, emacs org-mode, wunderlist and trialled a dozen other task management programs.
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 da…
hmm interesting idea. I've been trying all kinds of different tools for documenting my work/code snippets/notes.... But nothing sticked. Mind explaining more on that? Would it be stupid to have a wiki like system inside jupyter?
As a programmer, there is no larger time saver than having notes for code snippets, configuration file examples, etc.
I used to use Evernote, then I wrote a personal version of Evernote in Clojure that worked really well for me, except everything was just on my primary laptop. G Suite is not great from a privacy standpoint (but I can live with it) but for me wins out for convenience - well worth $12/month.
EDIT: I used to keep Jupiter-lab running on a GPU leased server for machine learning educational projects. If I still did that, as other people here have pointed out, with the new file interface Jupiter-lab would be a good choice, esapecially with some customization to implement a global search to find stuff quickly in all notebooks.
Earlier quoted context omitted.
I don’t “expect” the authors to do anything. But I am not going to spend many hours of my time reading a book when I see that the book is not maintained because there are many great books on my backlog that ARE being maintained by the authors/community.
All of my books are in pdf and receive zero maintenance - many of them are still incredibly useful.