Category Archives: Productivity

Introducing Page-o-Mat

As I mentioned in my post about recurring journals, I decided to write a python program to create a PDF that implemented my riff on the Da Capo journal. I finished it enough to share, and put it on GitHub. It’s called Page-o-Mat.

To make it more generally useful, instead of hard-coding this particular journal, I made it read a configuration file that can be used to describe lots of journaling styles.

Right now, the paper and page types are what I needed for my 2023 journal. I am about to do a test-run with getting it printed on LuLu. After that, I might make some more page templates.

The config file is in YAML. You could just list each page you want one-by-one, but to make things easier, there are a few ways to create enumerated pages.

  • Any page could have a count, which just repeats that page
  • Any page can have a variant list, which repeats the page, setting a variable that can be used in titles
  • Pages can have lists of sub-pages, and so on.
  • Pages can have sections

In the code, it’s implemented with nested loops and recursion. The indices of those loops are exposed to the config to use in date math, so that any section of any page can have a date calculated for it. Most journals would probably have sequential dates, but a recurring journal wants you to keep cycling back to the beginning of the book, so the date math is fairly complicated.

There are documented examples in the repo that (hopefully) explain this better. Start with daily.yaml, which is just a 365 page daily journal. 2023-recurring-journal.yaml shows the more complex example.

Recurring Journals

A few weeks ago, I backed a Kickstarter for a ”Day-based Journal”. The idea is that each spread of two pages represents a day of the month. For example, when you open it up, the left page has boxes for Jan 1, Feb 1, March 1, April 1, May 1, and June 1. The right-hand-side has July 1 … December 1. So, to journal in January, you turn pages for 31 days and then go back to page 1 to start February. You go back to page 1 to start March, and you can see each day in January and February as you progress.

This has two effects:

  1. You see your notes over and over (this reminds me of spaced repetition)
  2. You can see monthly progress and eventually a years worth of progress

I love the idea and hope it gets funded, but in the meantime, I’ve started designing a riff on this idea that I will probably print out for 2023 on LuLu.

As a prototype, I drew something similar to the Kickstarter for 62 pages of my current blank journal to cover the rest of the year (Sep-Dec).

Prototype of a recurring journal showing Sep 1, Oct 1 on left hand page and Nov 1 and Dec 1 on right hand page
Prototype of a recurring journal

Since that’s just four months, each box is much bigger — half a page each month to make up the two-page spread. For me, I think that’s the minimum size. I don’t think I could use the orignal Day-based journal as a primary way to journal, since I need space to do a time block for the day.

The next thing I noticed was that each day was a different day of the week. That is mentioned as a plus in the Kickstarter, but I think in weeks. So, for me, it would be much more useful if each day shown on the spread were the same day of the week. My Mondays are very different from my Fridays, and the weekend is nothing like a weekday.

So I started to sketch out what a 2023 Week-based ”Recurring” Journal might look like.

My solution so far is to run 2023 as 4 sets of 13 weeks. That’s 364 days, and since Jan 2 is a Monday (and I start my week on Mondays), I’ll treat Jan 1 as a special day and then make 2-page spreads for the rest of the year where each box is 13 weeks apart.

One downside is that they are not aligned to months or quarters, but that’s just the nature of weeks, and I want to embrace weeks. I decided to further sub-group the 13 weeks as 4, 4, and 5 week blocks. That’s almost a month, and while it’s not ideal that they are uneven, I am also embracing the 13, so I have to accept its primeness.

Also, you are only revisiting your notes every 13 weeks instead of every month. To address this there will be 28 summary pages with 13 boxes where you try to get the essence of the day. To get 13 equal sized boxes, I’ll borrow from Betsy Ross and just use horizontal stripes. I think this would be the best way to use the original Kickstarter journal.

I’m currently building a spreadsheet where I can plan out what each page of the journal will be. In addition to daily pages, there will be pages for planning and retros. I also want enough blank pages for random note taking. So far it’s over 300 pages.

When that’s done, I’m going to build a python script to generate the PDF for the interior pages. I will open-source it, so if you are interested, then watch this space.

Banking Blog Posts

Today is January 28th at 6:45pm. This blog post will be posted on February 10th at 10am.

This morning, I wrote a review of The Practice which published on February 9th. In that post, I mentioned that I published 30 posts in the last 30 days, but, I wrote those 30 posts in 19 days, and set them up to publish over 30 days.

Since I’ve been actively reading and writing notes, I have a big backlog of ideas and nascent writing. Blogging has been mostly about assembling these notes into posts, and banking them has taken all of the pressure off in trying to blog every day. With the pressure off, I sometimes write a couple of posts a day.

I have a few other tactics I use to make sure I publish every day, which I’ll post in the next few days (but I’ll write them right now).

Robotic Pair Programmers

If search engines ever get eclipsed, I think it will be by something in the environment that just brings things to your attention when you need them. I want this most when I code, like a pair programmer that just tells me stuff I need to know at exactly the right time.

When I’m in Xcode, there are so many times when I need information I don’t have. To get that information, I need to initiate a search. It breaks my flow to do this.

What I want is that information to just be in the environment.

One way this already happens with with code comments. In my source, I trust all of the editors, so I would like to see all of their comments and commit messages. This is actually possible if I turn on the Authors sidebar in Xcode.

But, what more could I get? Let’s say I index every Xcode project in GitHub, every iOS tutorial, every iOS question in Stack Overflow. Could that be distilled somehow and then shown to me at the right time?

One way that seems fruitful to me is rare API calls. There will be times when I am using an API that appears very infrequently in the corpus or my own repositories. In that case, it should infer that I probably need more help than usual and offer up a tutorial or the top Stack Overflow questions.

Another trigger might be my new comments. If I comment before I code, then it should be interpreted as a search query:

// Parse the JSON I get back from the data task

That should bring up links to likely API classes in the help pane (just like it would if I already knew the class). Maybe offer up imports to auto-add. Maybe offer a snippet. In Xcode it would be similar to the auto-suggested fixes for compiler errors.

This is just the beginning, and we can do a lot more. Whatever we do, we need to make sure that nearly every suggestion is useful, because we risk knocking the developer out of flow. Conserving flow should be the driver for how this works.

My Habit Totem for Daily Routines

In Environment Hacking, I wrote:

In [the Fogg Behavior Model], we add prompts to our environment for things we want to do more […] changing our environment to influence our own behavior. I have been thinking of “habit totems” I can put into the environment to prompt me.

So, in the past, when I’ve tried to institute daily startup and shutdown routines, it would fall apart eventually because I didn’t remember to do it. It was a partial habit at best.

So, this time, I designed a custom bookmark. I use them in my journal, my sketchbook, and any book I’m reading. Here it is (I got them made on VistaPrint):

The words under each routine are a short-hand. “Breathe” means meditate, which could be with the Breathe app on my watch, or any other way. “Practice” means to do my daily practice of coding, writing, and sketching. Hone is my yearly theme.

In practice, the biggest help is to remember to plan the next day. It only takes a few minutes, but makes all the difference.

I tried to think of something clever to put on the back of the bookmark, but I was so indecisive about it that I finally just stuck a photo I took of a Florida beach sunset and called it a day.

End Your Week with a Plan for Next Week

This is a follow up to my end-of-day tomorrow planning.

I run my weekly plan Monday-Sunday, so sometime on Sunday I’ll start to make my plan for the upcoming week.

The first thing I do is collect my WINS from my daily plans. At the end of each day, I tried to pick out something from the day that would bring me joy to reflect on later. Now (at the end of the week) is later.

Under that I put a BIG 3 checklist for the week. These are tasks I commit to do the following week. Each might take several days, so I need to break them down.

So, under that, I write the date of the next seven days on separate lines. I try to break down my Big 3 into tasks that need to be done each day that will eventually accomplish them. These will feed into my daily plans that week.

I’m not going to write a separate post for it, but I also have a monthly plan with a monthly Big 3 and biggest WINS. The entire thing rolls up to my yearly plan, which is a one-word theme and some high-level ideas of the kind of things I want to do that year. Months and years are not planned out as thoroughly as weeks and days—they are mostly a guideline to provide some direction.

Environment Hacking

I’m a big believer in changing your environment to influence your own behavior. I wrote in Self Control that I block social media, news, and other distracting sites on my work computers (I now do it on all computers and devices I use). This means I don’t need to expend any willpower avoiding those sites—it’s simply impossible to get to them.

I also use Due and my own app, Habits, to give me reminders to do things I want to do, but forget.

These apps are using what the Fogg Behavior model calls a Prompt. In this model, we add prompts to our environment for things we want to do more and remove them for things we want to avoid.

My blocking of social media is using the environment to impair my Ability, which is another variable you can affect by changing your environment.

Fogg covers this in-depth in his book Tiny Habits.

One of BJ Fogg’s insights is that you already have habits that are completely automatic, so he suggests using those as prompts for a new habit you are trying to build. You repeat to yourself, “After I do [some automatic habit], I will do [some tiny version of a new habit]”. For example, “after I brush my teeth, I will floss one tooth”. In this case, the environment is your existing habit.

This works great, but I have some habits that I can’t easily tie to existing one (or at least I haven’t been successful at it yet). For these kinds of habits, I have been thinking of “habit totems” I can put into the environment to prompt me.

One example is that when I run, my arms tend to cross-over in front of my body instead of staying out at the sides. If I notice it, I fix it, but I can’t get it to be top of mind while running. So, I cut out a small arrow out of electrical tape and put it on my watch band.

This has helped a lot. I see this part of my watchband a lot during my run, and it leaves enough of an imprint to help me keep my arms out.

The difference is the habit totem is location-based, rather than time-based (like an alarm) or behavior-based, like another habit.

Yearly Themes

I’m a proponent of yearly themes to tie together a general direction for the year. I was first exposed to this idea from Gretchen Rubin and Elizabeth Craft’s Happier Podcast. It’s also a recurring topic on Cortex with Myke Hurley and CGP Grey. Here’s a video CGP Grey made about it:

My theme for 2021 is Hone. I am mostly fine with the things I am doing, but I just don’t do them enough. 2021 is about doing them more deeply and getting better at them.

I want to run more seriously, and since we might be able to race again in 2021, I’d like to try to set some PRs.

I am going to write more. My goal is quantity because I think that will be the best way to improve. To drive this, I am reading and note taking more diligently.

I have been sketching for years, but not often enough to improve. Now, I am setting aside at least a little time every day to sketch. One easy way to start this is blind sketching, where you look at the subject and not the paper at all. It lowers the bar enough to make it an anytime activity.

I became mostly vegan in 2019 for health reasons. My cholesterol is now normal, but I want to lower my oil and processed fat intake as well to see if I can get it even lower.

So, I am grouping this all together as HONE, which I interpret as sharpening via repetition.

End Your Day with a Plan for Tomorrow

I keep a physical daily journal in an A5 Dot Grid book. At the end of each day I draw a template for the next day and try to fill in as much as possible. For example: on January 18, I drew this for the 19th.

The red checklist at the top is three things that I must get done that day (The Big 3). This is reserved for my most important tasks. If I can’t commit to three, it’s ok, I can use one or two, but never more than three.

Then, below that are my time blocks for the morning and work-day. If I have meetings, I’ll put them in, and then I try to find a couple of big blocks to work on my Big 3. It’s ok for this to be a little blank the night before, but sometime in the morning it will be mostly filled in.

Under that I’ll keep a running list of tasks and notes for the day as a bullet journal.

This technique is a result of refinement over time derived from a combination of Free to Focus and Deep Work, both highly recommended.

I have a variant of this that I do at the end of the week that I’ll post about soon. One element of the weekly plan is to collect my WINS from the week before, so at the end of each day, I try to pick out one or two things I did that will bring me joy later when I reflect on them.

Self Control

Since my computer is factory equipment, I consider its ability to show me news and social media a defect. One easy fix is to edit /etc/hosts to block these sites, but that’s reversible by just re-editing it. A year ago I found an app, SelfControl, that takes these edits out of my hands.

To set it up, you give it a list of blocked sites. Then, when you start it, it will put entries into /etc/hosts that sets their IP addresses to 0.0.0.0. If you remove these entries, it will keep reapplying them. And since it asks for privileges, it can do this in a complex way. You could thwart it if you wanted, but it’s enough of a pain that you probably won’t bother.

After using it for a while I added a few practices that make it more useful.

  1. I use the Due app on my iPhone (and Watch) for simple recurring reminders. I set up a morning reminder to restart SelfControl.
  2. I went into my /etc/hosts and made a copy of the SelfControl section (it’s clearly marked with comments) and made it a permanent part of my hosts file. I italicized permanent because I can edit this part, but it’s there to be a little bit of a deterrent if I try to go to any of these sites in a non-blackout period.
  3. At the end of the week, RescueTime sends me an email with a summary of my productivity. I can easily see if any new distracting sites are taking significant time and add them to SelfControl.
  4. I found an app for iPhone called Zero Willpower that does the best it can to replicate SelfControl on the iPhone. It’s essentially a content-blocker that you can edit and a timer you can set to disallow deleting. On the iPhone there is nothing they can do to stop you from removing the app or disabling its content blocking privileges, so thwarting it is easy if you want. Again, it’s enough of a pain, that it’s enough to keep me off distracting sites.