There’s a tool I’ve been interested in using (if it exists), basically a jupyter notebook, but which saves all outputs to tmp files (possibly truncating at the 1MB mark or something), and which maintains a tree history of the state of cells (i.e. if you hit ctrl-z a few times and start editing, it creates a branch.) Neither of these are particularly memory heavy, but both would have saved me in the past if they were hidden options to restore old state.
I’d also add that if you had a bug, and it took real effort/digging to find an online solution, archive the link to that solution in a list (preferably with date tags.) This has been preferable for me over painstakingly re-searching / trying to search through browser history when needed.
Hm, I think this tool would’ve been really helpful for me in the past for a couple of occasions. Usually if I want to save a cell output, I just won’t edit that cell and I’ll create a new one, even if it means redundant code.
Also +1 on keeping track of bugs! I should’ve added to the og post that one thing I do that’s really helpful for me is keeping track of procedural knowledge (i.e. how to setup a GPU, how to fix common issue X, etc.) in a personal Slack that I’ve created as a second brain basically. I found that I used the message-yourself-in-slack feature a lot to keep track of small notes for myself, and since I did it so much, I created a whole private, personal Slack and that’s been pretty useful in keeping track of bugs, etc.
There’s a tool I’ve been interested in using (if it exists), basically a jupyter notebook, but which saves all outputs to tmp files (possibly truncating at the 1MB mark or something), and which maintains a tree history of the state of cells (i.e. if you hit ctrl-z a few times and start editing, it creates a branch.) Neither of these are particularly memory heavy, but both would have saved me in the past if they were hidden options to restore old state.
I’d also add that if you had a bug, and it took real effort/digging to find an online solution, archive the link to that solution in a list (preferably with date tags.) This has been preferable for me over painstakingly re-searching / trying to search through browser history when needed.
Hm, I think this tool would’ve been really helpful for me in the past for a couple of occasions. Usually if I want to save a cell output, I just won’t edit that cell and I’ll create a new one, even if it means redundant code.
Also +1 on keeping track of bugs! I should’ve added to the og post that one thing I do that’s really helpful for me is keeping track of procedural knowledge (i.e. how to setup a GPU, how to fix common issue X, etc.) in a personal Slack that I’ve created as a second brain basically. I found that I used the message-yourself-in-slack feature a lot to keep track of small notes for myself, and since I did it so much, I created a whole private, personal Slack and that’s been pretty useful in keeping track of bugs, etc.