What does that look like, day-to-day? Here's what a typical day might be:
I wake up at around 8 or 9 after an average of 8.3 hours of sleep (although in November, the average was much higher). I stay in bed another twenty minutes or so, easing myself into wakefulness. During this time, I might do a quick scan of blog posts, Hacker News, Reddit, Facebook, and my e-mail. Sometimes I think of a few ideas I would like to explore that day, and I type that into Evernote on my phone so that I don't forget.
Eventually, I leave the warmth of the duvet, slip into a fuzzy bathrobe, and head downstairs for breakfast. I feed the cats, too. After breakfast, I head back upstairs to brush my teeth and take care of other morning routines. I return to the kitchen (often still in pajamas), open my computer, and think: What do I want to think about today? What do I want to learn about? I look at my lists and outlines for ideas.
Depending on what I feel like doing, I might spend some time programming or writing. If I don't feel particularly creative, I might read instead. I review my Org Mode agenda in Emacs to see what I need to take care of today, and I check my other lists for unscheduled tasks that might be good to do too. I keep my notes in large, lightly-structured text files so that I always have something to work on.
Here's the important part of my routine, I think: I'm almost always taking notes. I keep a text file open on my computer as I program or debug, writing down the things I'm considering or where I'm getting stuck. I write, and I write about writing. Even when I'm away from my computer, I try to write brief notes on my phone.
People often think that taking notes takes too much time and slows you down. I find that notes help you cover more ground. When I don't take notes, I get frustrated because I can feel my brain trying to jump from one topic to another too quickly. I forget. I have to figure things out again. Notes help me a lot. They don't even have to be complete notes. Sometimes a phrase or two is enough to help me get back from interruptions or pick up loose threads.
I publish as many of my notes as I can. They often help other people, and I get to learn even more from the conversations on my blog. Publishing my notes also makes them easier to back up and search.
Back to my daily routines. At some point in the afternoon, I might respond to e-mail. I usually try to do this at least once a week, although sometimes I let it slip for longer. Sometimes I nap or take a break. Then I check in with myself again: What do I feel like working on now? There's often a little time to get another chunk done before dinner.
We go to the library and the supermarket a few times each week. Sometimes we cook; sometimes we have left-overs. Evenings are for tidying up, taking care of things, and relaxing. Sometimes I read books I've borrowed from the library, or spend some more time writing, or play video games, or practise sketching.
When I go to bed, I catch up with W- and then read a little: often something unproductive but fun, like fanfiction with a rational bent.
After we turn out the lights, I wrap up by thinking a little about how I would like the next day to turn out: What do I need to do? What do I want to learn? What would make things even better? I dream my way into the next day.
I think I do less than many people do. I feel like I live at a more relaxed pace. Still, my weekly reviews show me more crossed-off tasks than I expected. My monthly reviews show that I keep moving forward on my plans. Whenever I do my annual reviews, I can see some difference between the past and the present. So maybe it's not that I'm particularly efficient at doing things, but I'm good at keeping track of the progress.
I share my time data publicly, so if you're curious, you can dig into it and find out more about what a typical day is like.
I don't think I have any awesome productivity secrets. I live on the same 24 hours as everyone else. But I enjoy asking questions, taking notes, looking for opportunities for little improvements, and sharing what I learn along the way, and I think that's what people respond to. If I can do this with a fairly relaxed pace, you can probably do something similar with your life too. =)
Related:
Separate files
You can put different things in different files, of course. I use a few large Org files instead of lots of small ones because I prefer searching within files rather than searching within directories. Separate files make sense when I want to define org-custom-agenda-commands
that summarize a subset of my tasks. No sense in going through all my files if I only want the cooking-related ones.
What would help me make better use of lots of files? I can practise on my book notes, which I've split up into one file per book. It's easy enough to open files based on their titles (which I put in my filenames). But I don't have that overall sense of it yet. Maybe #+INDEX:
entries, if I can get them to generate multiple hyperlinks and I have a shortcut to quickly grep across multiple files (maybe with a few lines of context)? Maybe a manual outline, an index like the one I've been building for my blog posts? I can work with that as a starter, I think.
Okay. So, coming at it from several directions here:
helm-do-grep
works, but my long filenames are hard to read.Outlines
Within each file, outlines work really well. You can create any number of headings by using *
, and you can use TAB
to collapse or expand headings. You can promote or demote subtrees, move them around, or even sort them.
I generally have a few high-level headings, like this:
* Projects ** One heading per current project *** TODO Project task * Reference Information I need to keep track of * Other notes * Tasks ** TODO Lots of miscellaneous tasks go here ** TODO Lots of miscellaneous tasks go here ** TODO Lots of miscellaneous tasks go here
Every so often, I do some clean-up on my Org files, refiling or archiving headings as needed. This makes it easier to review my current list of projects. I keep this list separate from the grab-bag of miscellaneous tasks and notes that might not yet be related to particular projects.
I use org-refile
with the C-u
argument (so, C-u C-c C-w
) to quickly jump to headings by typing in part of them. To make it easy to jump to the main headings in any of my agenda files, I set my org-refile-targets
like this:
(setq org-refile-targets '((org-agenda-files . (:maxlevel . 6))))
How can I get better at organizing things with outlines? My writing workflow is a natural place to practise. I've accumulated lots of small ideas in my writing file, so if I work on fleshing those out even when I don't have a lot of energy–breaking things down into points, and organizing several notes into larger chunks–that should help me become more used to outlines.
Tags
In addition to organizing notes in outlines, you can also use tags. Tags go on the ends of headings, like this:
** Heading title :tag:another-tag:
You can filter headings by tags using M-x org-match-sparse-tree
(C-c \
) or M-x org-tags-view
(C-c a m
).
Tags are interesting as a way to search for or filter out combinations. I used tags a lot more before, when I was using them for GTD contexts. I don't use them as much now, although I've started tagging recipes by main ingredient and cooking method. (Hmm, maybe I should try visualizing things as a table…) I also use tags to post entries under WordPress blog categories.
How can I get better at using tags? I can look for things that don't lend themselves well to outlines, but have several dimensions that I may want to browse or search by. That's probably going to be recipe management for now. If I figure out a neat way to add tags to my datetree journal notes and then visualize them, that might be cool too.
Links
Org Mode links allow me to refer not only to web pages, files, headings, and text searches, but to things like documentation or even executable code. When I find myself jumping between places a lot, I tend to build links so that I don't have to remember what to jump to. My evil plans Org Mode file uses links to create and visualize structure, so that's pretty cool, too. But there's still a lot more that I could probably do with this.
How can I use links more effectively? I can link to more types of things, such as Lisp code. I can go back over my book notes and fill in the citation graph out of curiosity. Come to think of it, I could do that with my writing as well. My writing ideas rarely fit in neat outlines. I often feel like I'm combining multiple threads, and links could help me see those connections.
In addition to explicit links, I can also define “radio targets” that turn any instance of that text into a hyperlink back to that location. Only seems to work within a single file, though, and I've never actually used this feature for something yet.
Properties
You can set various properties for your Org Mode subtrees and then display those properties in columns or filter your subtrees by those properties. I've used Effort
to keep track of effort estimates and I have some agenda commands that use that. I also use a custom Quantified
property to make it easier to clock into tasks using my Quantified Awesome system.
I could track energy level as either tags or properties. Properties allow for easier sorting, I think. Can I define a custom sort order, or do I have to stick with numeric codes? Yeah, I can sort by a custom function, so I can come up with my own thing. Okay. That suggests a way I can learn to use properties more effectively.
There are even more ways to organize Org Mode notes in Emacs (agenda views, exports, etc.), but the ones above look like good things to focus on. So much to try and learn!
]]>