Workflows
Need to aspire to reach this level.
Entry Point
"What should I be doing?" - The moment I ask myself that, open the calendar.
Tracking time and how its used is more impactful than scheduling tasks to the minute detail. It is better to block time for specific things and then track what was actually done at the end of the week.
Note what needs to be done
- Project related TODOs in projects.org
- Other TODOs in agenda/inbox.org
Schedule time for what needs to be done
- Schedule TODOs using
C-c C-s, send to Google calendar viaorg-gcal-post-at-point. - Assign deadlines using
C-c C-d. - Refile meetings to phd/meetings.org
Doing the work
- Clock in via
C-c C-x C-i - Clock out via
C-c C-x C-o
Chunk time of day in calendar in 1 or 2 hour blocks. A chunk should represent one of the following:
Rather than labelling a chunk as Meeting, Research, Reading etc, maybe its better to block time by project name. E.g. Causal Elicitation: Reading (remember to create an org-roam entry and link to it in data/projects.org), Stackelberg Interventions: Meeting (remember to create a meeting note in meetings.org with pre-meeting, during meeting and post-meeting notes) etc. Things like Coursework (put link to org-roam entry), Gaussian Process Teaching (put link to relevant Slack, zulip etc), Errand (e.g. cleaning room, buying groceries etc), Administration, Leisure (Meeting with friends, going for a walk, reading in a caf'e etc) then follow nicely. Can also have things like Learning: Differential geometry, Learning: Parser Combinators etc. Also a general entry with something like "Outside scope: Reading" for catching up with literature outside of current research scope.
Color codes
Current (Google calendar) colour codes are:
- Black:
- Red: Medical
Journaling
Write a journal entry with org-capture, detailing the following:
- What am I grateful for?
- What is my most important task today?
- What story-worthy moment happened yesterday?
- How am I feeling today?
- What's working right now? What could be better?
Project Management
- Peter Jones's blog post.
- Break down things into features (for which workload is hard to estimate), then tasks for the features (which are easy to estimate). If a task takes around a day, break it down, ideally maximum 5 hours per task.
- Use org-mode column-view to see times nicely.
Literature Review/Notes
- To get the conference/journal versions of arxiv papers, see script from this video.
- Create Anki notes for org-roam nodes when possible under a * Anki heading. See Anki notes for more information.
Writing
Coding/Experiments
Presentations
Music
- IDN tag changes names of files and tags them with the artist name - possible workflow could be Spotify \(\to\) YouTube \(\to\) MP3 \(\leftarrow\) IDN script, followed by post-processing like renaming.
Desiderata:
- Ability to take a Spotify playlist and collect corresponding MP3s (e.g. via YouTube).
- Ability to take a YouTube playlist and collect corresponding MP3s.
- Some script (maybe own one) to rename files by replacing underscores with spaces etc if needed.
- Ability to tag genres automatically.
Some potential issues:
- ffmpeg does not find song in YouTube.
- Language - want Greek songs in Greeklish (Greek + English) instead of in Greek.
Some links:
- audacious.el - emacs interface to audacious.
- deadbeef - multiplatform, handles tags etc.
- beets.io - Python based music collection manager, has many plugins as well.