11–20 of 159 posts
As a data scientist I often run code that takes hours, and getting a slack message when it finishes is super helpful, and it has often helped me catch when a script finishes too early due to some error.
One of my favorite automations is a slack bot I made to send me a message when a process finishes: https://github.com/spohngellert-o/SlackProcessTrackerBot As a data scientist I often run code that takes hours, and getting a slack message when it finishes is super helpful, and it has often helped me catch when a script finishes too early due to some error.
function notifyme() {
MSG=${1:-'Terminal is done'}
TITLE=${2:-"Done!"}
osascript -e "display notification \"${MSG}\" with title \"${TITLE}\""
}
bin/start-unit-tests; notifyme
I created a script to tarball my git server's git directory, encrypt it, and backup to Google Drive if new commits were made that day. inb4 "just use GitHub"
Automatic monthly purchases of low-cost index funds.
This way I don't have to worry (too much) about over-spending on other items as I've taken care of future-me.
Journaling. I have a shell script that that creates a new markdown file for that day, which I write my journal entry into. Another script compiles a year's worth of journal entries into an epub. Another workflow I made is similar, but for tasks. So every day I run a shell script that copies the last day's tasks to a new file with the new day's date, forcing me to evaluate what was done the previous day (if anything).…
I've tried org-journal in Emacs but I could never get over the learning curve of Emacs + org-journal.