Morning, afternoon, evening, commute: thinking about what to do when (sketched)

My days have regular rhythms, as yours probably do. In the morning, I’m usually fresh and energetic. The afternoons are sometimes a little slower, but they’re often solidly productive. In the evenings, my mind is a bit tired, but it’s a good time to catch up on chores.

2014-12-11 What is good for me to do when

I’m slowly learning about the quirks of my rhythms and choices. I’ve been thinking about what’s good to do when so that I can find better ways to use my time.

  • If I commute off-peak, I can sit down and write or play games. It’s easy to time this in the mornings. I often plan to avoid the evening rush, but I get stuck in it anyway. This is because I get distracted by cool things to work on or learn. Maybe I should set an alarm.
  • If I sit on the couch, one of the cats will usually settle onto my lap. This makes typing on a laptop inconvenient. But I enjoy spending time with the cats, so I don’t mind giving up a little productivity. It’s relaxing to focus on the cat instead of multitasking, and sometimes ideas float into my head. When I want to work on something, my phone can be more convenient than my laptop.
  • If I do a coding sprint close to midnight–say, from 9:30 PM to 11:30 PM–I have a harder time falling asleep, even if I’m no longer thinking about code. If I spend the same time writing, even on my computer, I’m fine.

Geeking out with W- is a good way to spend evenings. Brush up tech skills, spend time together, make the house a little smarter.

I hadn’t realized how similar cat-couch-time is to commuting time. I should be sure to keep my phone handy. Differences: drawing on my tablet PC is something that makes decent use of cat-couch-time that I wouldn’t do while commuting, and I can listen to podcasts while commuting but I’d rather listen to purring when with the cats.

Hmm. This gives me a way to practise using my time better during each phase of my day. I might print this and keep it handy, or bookmark it and refer to it often.

On a related note, what’s good for me to do on which days of the week? Hmm…

  • Saturday: Groceries, laundry, tidying, library, weekly review, meeting friends
  • Sunday: Cooking, meeting friends
  • Monday: Writing, coding
  • Tuesday: Consulting, because of team meeting; Hacklab open house
  • Wednesday: Packaging, drawing
  • Thursday: Consulting, because of team meeting
  • Friday: Accounting, paperwork, correspondence, transcripts, review, planning

What would your rhythm look like?

Review: Week ending January 2, 2015

This week was about making little improvements. We installed weather-stripping to stop the drafts under the exterior walls. We added more lights to the basement, including an undercabinet light at my desk. I organized the tangle of USB cables plugged into a hub behind my monitor, tucking them into a box with a few input and output holes so that there’s less visual clutter. I also set up my Cintiq 12WX again. Using it to draw book sketchnotes is more pleasant than using my tablet PC. I wrote some Emacs Lisp to help me with my monthly reviews, and some Javascript to add blog links to more than a hundred of my sketches. I set up a Tasker scene to help me track my time on QuantifiedAwesome.com with just two clicks. Fun!

I posted my annual review. I think my focus for 2015 is going to be on little improvements and micro-habits. Getting really good at that will likely have all sorts of benefits.

Next week, W- will be back at work, and I’ll probably spend Thursday consulting. The rest of the time, I’m looking forward to revising transcripts, sketching books, and planning my next series of 2-4 week experiments.

Blog posts

Sketches

Link round-up

Focus areas and time review

  • Business (12.6h – 7%)
    • Earn (2.4h – 19% of Business)
      • Earn: E1: 1-2 days of consulting
    • Build (4.8h – 38% of Business)
      • Drawing (2.9h)
        • Sketchnote So Good They Can’t Ignore You
        • Sketchnote The Checklist Manifesto
      • Delegation (0.0h)
      • Packaging (0.0h)
      • Paperwork (0.0h)
        • File payroll return
      • Fix forgot password process
    • Connect (5.4h – 42% of Business)
  • Relationships (39.5h – 23%)
  • Discretionary – Productive (11.6h – 6%)
    • Emacs (2.1h – 1% of all)
      • Revise transcript for Magnar Sveen
      • Revise transcript for Thomas Kjeldahl Nilsson
      • Reach out to possible Emacs Chat people
    • Get Org Mode to talk to my Vagrant VM
    • Make something that updates my Flickr photo descriptions in bulk
    • Write Emacs Lisp code for monthly review
    • Get passport pictures
    • Apply for passport
    • Pick up cultural access pass from Front and Parliament
    • Writing (7.9h)
  • Discretionary – Play (12.3h – 7%)
  • Personal routines (23.4h – 13%)
  • Unpaid work (8.8h – 5%)
  • Sleep (59.9h – 36% – average of 8.6 per day)

2014 in review

First, a list of posts I particularly want to remember from this year. If any of them sound interesting, feel free to check them out – I’d love to hear what you think.

Second, a snapshot of everyday life, so that I can remember what it was like at this time. My routines haven’t changed much since last year, except perhaps that I spend more time writing, cooking, and snuggling with W- and the cats. I try to drop by my consulting client on Thursdays, having successfully off-loaded most of my responsibilities to the team members I’ve trained. I go to Hacklab most Tuesdays to help cook a free vegan dinner for the open house; it’s enjoyable cooking practice, and sometimes I get interesting conversations out of it. W- has taken on a bigger role at work, but that still gives us plenty of time for family projects (we’re working on the basement at the moment). J- often has friends over to study and hang out, so we keep the house stocked with a variety of snacks.

Some memories from this year:

  • We took our cat Leia for a lion cut to deal with some of the mats in her fur. It was very amusing.
  • I started keeping a more deliberate private journal using Org Mode and Evernote. It’s a good complement to blog posts.
  • Mixed results in the garden, but we were pleasantly surprised by getting one zucchini, two bitter melons, and two winter melons out of it. We’ll keep trying.
  • I became a Canadian citizen! I’ve been remiss about actually applying for the passport, though. I’ll get that sorted out soon.

2014-12-25 2014 Review

Third, overall themes:

In 2013, I resolved to spend more time focusing on my own things instead of giving in to the pull of consulting. So in 2014, I collected more resources into e-books (and even one print book). I experimented with writing a four-part course. I took a Coursera class on analyzing data with R. I played around with Emacs and wrote blog posts for hours.

And yet my data tells me I actually spent more time working on other people’s projects. It went from 9% of my time in 2013 to 12% of my time in 2014, which works out to about six additional hours extra per week. This is coincidentally the same number of hours I reduced my socializing by, although a chunk of that can be explained by shifting socializing to Hacklab (which I track under Business – Connect).

The special project I did in September really changed the balance (27.5% of my time in that month!), as did the fact that I didn’t take any month-long breaks. Even hermit-mode November involved working from home 6% of the time (~10 hours a week).

It’s funny how perception doesn’t match data. Despite the extra time spent consulting, I felt a lot more self-directed this year – maybe because I produced more tangible stuff, and my tasks were more aligned with each other. But I’m drifting off course from becoming my own main client, and I want to adjust that heading in 2015.

Category 2014 % ~h/wk 2013 % ~h/wk change in h/wk
Business – Earn 12.4 21 9.1 15 6
Personal care 14.6 25 12.7 21 4
Discretionary – Productive 7.8 13 6.7 11 2
Sleep (~ 8.9h per day) 36.4 61 36.7 62 -1
Business – Connect 4.2 7 4.4 7 0
Business – Build 7.0 12 7.5 13 -1
Unpaid work (chores, etc.) 7.0 12 7.8 13 -1
Discretionary – Play 5.0 8 5.2 9 -1
Discretionary – Family 4.0 7 5.5 9 -2
Discretionary – Social 1.2 2 4.9 8 -6

Data collected using Quantified Awesome – compare 2014 and 2013

In terms of technical skills, I picked up more experience in:

  • Tableau: I learned how to take advantage of custom SQL and filter actions, and I became more comfortable with calculated fields, parameters, and filters.
  • Javascript: I got better at writing short Javascript functions and testing them. The new API for the social platform I work with on my consulting gig allowed me to build all sorts of nifty new tools. I’ve also been helping another developer pick up skills.
  • NodeJS and AngularJS: I built a prototype survey tool that also automated other things we wanted to do during a special event.
  • Rails 4: I finally upgraded quantifiedawesome.com to Rails 4.

Also, Emacs Chats and Emacs Hangouts have been awesomely fun and inspiring. Can’t wait to set up more of them!

In terms of writing, I got better at working with outlines as a way to organize my thoughts within each blog post. I’m still working on getting the hang of outlines to help me organize my thoughts across multiple blog-post-sized chunks, but the basic Emacs Lisp course was a good start. I also started building up an Emacs Org to EPUB/MOBI/PDF workflow for quick publishing and updating, so that I can can get more e-books up on Gumroad. Because I offer these resources on a free/pay-what-you-want basis, every time someone does buy it, I’m delighted to have that opportunity to connect.

My 2013 review included a number of themes:

  • Smooth consulting transitions: We’re on the way there, I think. I’ve been training one of the team members to cover the work I used to do, which is great.
  • More initiative-taking: Yes, especially in terms of professional development and publishing. I’m getting better at figuring out what I would like to learn and how to try things out.
  • Cardio and strength exercise habits: W- shared the Couch-to-5K program he picked up at work. We’d gotten all the way through it together (even though I covered much less distance than he did), but then I had to drop the habit because of other considerations. I’d also started the Exercise Ladder, but it got hit by the same restrictions. We’ll see how next year turns out! It’s good to know that I can do it and enjoy it, and I’m looking forward to starting even if I have to start from scratch.
  • Intentional interaction: I love spending time with W-. I’ve also been spending more time connecting with people in person at Hacklab open houses (at which folks are welcome to visit me, too, so it’s a great way to have low-commitment conversations). I feel great about my online conversations, too; there’s resonance there.On the flipside, I spent less time setting up get-togethers in person or treating people to lunch. I didn’t bother with a birthday party for the second year in a row; I realized I enjoy the peace and quiet.

    I’ve been pulling myself in, focusing on a small core. Still, compared to last year, this year’s interactions feel more natural and more relaxed for me. Perhaps I’m more selfish and withdrawn than the ideal, but I’ll grow at my own pace. I’m probably going to stay similarly reserved in 2015 to give myself space to explore things, but I’ll reconsider this in 2016.

  • Simple living: Wow, Epictetus, dude. You do make it easier to separate what’s important and what’s just nice to have. Aristotle has a lot to say about the good life, and Seneca has something to say about the short life. Good stuff.This year, I let go of quite a few anxieties, attachments, previously-unexamined commitments, and desires. I am getting a little attached to flexibility, though, so that’s something I may want to experiment with.
  • More harvesting and sharing: That worked out well. I’m excited about writing bigger chunks with outlines and using my publishing workflow to package even more useful resources. This will be fun.

It’s been a good year for the stock market, although all of that is still paper gains for me since I haven’t sold any stocks and all my dividends are reinvested. We had some pretty large expenses (in line with our priorities, at least) that required me to dip into my savings. I issued my first dividends last year, so if things work out the way I expect them to at tax-time, planning should be smoother.

Here’s a more detailed time breakdown of some things I care about:

Activity 2014 % 2013 % Change in hours/year
Emacs 1.8 1.1 61
Drawing 2.6 2.2 35
Writing 3.2 3.0 18

Hmm. I didn’t spend that much more time, but it feels a little awesomer this year; the posts grew into more conversations with people, and I learned more from those. Maybe it’s that test-driven learning thing. What you learn becomes more real to you and more useful to others when you create something from it, so it can make sense to aim for creating something from the beginning.

I’m getting a little clearer about what I want to do with my writing, drawing, and Emacs-tweaking:

  • Learn more stuff myself: Because this is fun and it tickles my brain
  • Delight and inspire people with the cool stuff out there. (Selfish reason: I get to learn, too!)
  • Connect with people: something about resonance and swapping notes and casting a little light on different roads…

Experiment update: 2015 will be the fourth year of my five-year experiment. Boggle! When I thought about what five years looked like in 2012, it felt like such a big space – more than university, more than the time I spent at IBM.

  • The first year, I learned how to experiment with business models, hitting the ground running with consulting.
  • The second year, I focused on consulting and event sketchnoting.
  • The third year (2014), I scaled down consulting so that I could learn more about creating.

2014 was the year that people’s generosity showed me that I really like writing as a way of creating value. There were countless conversations and even the occasional purchase of free/pay-what-you-want (PWYW) resources. I liked waking up in the morning to a notification that someone had decided to express their appreciation and invest in me (and themselves!). I liked the responses to my thank-you notes, the questions and suggestions and ideas. It was more of a gentle thrum rather than the highs and lows of programming, but I liked it.

If my life can continue to fit within investments and savings and little streams of income, I’d like to keep doing this. It’s not going to be an extravagant life, but there’s room for what’s important. So the fourth year, 2015, will be a good opportunity to explore sharing further. Can I keep this going through the extra uncertainty we might be dealing with next year? Can I create and receive value with this commitment to openness instead of following the trend toward exclusive courses and premium content? Can I build resources that will save or improve 10-100 hours of people’s lives so that they’re willing to give me the equivalent of a few of their hours to make this even better?

In 2015, I’m looking forward to:

  • Improving my technical skills:
    • Getting even more deeply into Emacs and taking advantage of the many useful packages that are available
    • Writing shorter, better-tested code in Javascript and Rails
  • Writing with even more resonance and helpfulness: digging deeper into the things I’m learning and sharing them with other people in ways that help and engage
  • Successfully taking on more uncertainty with even better safety nets and equanimity

It’ll be fun. =) Thanks for great year!

Previous reviews:

Learning a little more quickly

Sometimes I feel like I learn more slowly than I used to. Maybe my brain is a little fuzzier than before. That’s what it tries to tell me as an excuse, but I soundly reject that, because too much belief in that can lead to accepting more excuses. It’s more likely I’m spending time slogging through the plateau of mediocrity instead of playing on the slopes of awesomeness, and my brain is unfairly comparing the experiences of the two. Being aware of it means I can accept it as normal and deal with it.

I suspect this is happening because a quick antidote for the “Grr, my brain is so fuzzy” feeling is to hang out in help channels and answer people’s questions, or work on client projects and help them with their requests. Then I usually feel like I learn pretty quickly, especially when speed-reading and knowing what to search for and being able to combine different things means delighting people with how rapidly we can get stuff done. It’s ego-gratifying, but I shouldn’t do it all the time. It’s better for me to sit with my occasional frustration and get better at learning things on my own.

So it’s not that my brain is being particularly bleah, but that it wants to snack on small questions and quick wins instead of eating its vegetables.

This is where I stretch the metaphor and start thinking of ways to swap out some of the less-favoured vegetables for ones that are more palatable but just as nutritious, maaaybe letting it pick out a few things it doesn’t like and offering it options so that it thinks it’s choosing. Or something like that.

wpid-2014-11-12-What-are-the-things-I-want-to-learn-more-quickly-and-what-would-that-look-like.png

Hmm. That is an interesting metaphor, actually. It’s like I know there’s value in chewing your vegetables and all sorts of other good stuff, but I just want to start with dessert, or if I have to eat the rest of the stuff, maybe I can just pick the good parts and be off to the next thing. And I’m all, like, “I’ve already tried the green beans! Why do I have to eat them again?” (Actually, in real life, I get along fine with green beans. But you probably get the idea.)

So maybe the trick is to eat those vegetables and make “Mmmmmm!” noises until my brain gets the hang of it. Maybe even pretending that vegetables are coveted prizes. (“Good girl! Have a carrot / read an e-book.”)

Huh. Metaphors. Fun to play with. Surprisingly useful.

If you’ll excuse me, I’m off to read through a yummy Rails tutorial. Mmm. Fun. =)

Org Mode publishing workflow for Sketched Books collection

I want to publish things in chunks that are bigger and more logical than blog posts, so I’ve been experimenting with my ZIP/PDF/EPUB/MOBI workflow.

Org Mode, Calibre, and Vagrant are terrific tools. Org Mode lets me write easy-to-modify source that I can export to different formats, like HTML and LaTeX (with the Beamer package), which lets me use PdfLatex to convert to PDF. Calibre converts HTML to EPUB and MOBI. Since tools can be difficult to set up on Windows, I use Vagrant to set up a virtual machine running Linux and I share my working directory with it.

multiple-cursors was so useful when I was wrangling the directory listing into the right format for Org. I’m glad I learned how to use it!

Here’s a Makefile I put together that simplifies the process for me:

all: index.html sketched-books.epub sketched-books.mobi ebook.pdf sketched-books.zip

clean:
	rm -f *.dvi *.log *.nav *.out *.tex *.snm *.toc

distclean: clean
	rm -f Sketched\ Books.zip index.html *.epub *.pdf *.mobi

Sketched\ Books.zip: *.png index.html
	(cd ..; zip sketched-books/sketched-books.zip sketched-books/* -i *.css -i *.png -i *.html)

index.html: index.org
	emacs --batch -l build.el index.org -f org-html-export-to-html --kill
	cp index.html index.tmp
	sed -e "s/org-ul/org-ul small-block-grid-3/" -e 's/div id="content"/div id="content" class="columns"/' -e 's/class="status"/class="status columns"/' index.tmp > index.html
	rm -f index.html~ index.tmp

ebook.html: ebook.org
	emacs --batch -l build.el ebook.org -f org-html-export-to-html --kill

cover-base.png:
	montage *Sketched*.png -geometry -30-30 -thumbnail x400 -tile 6x5 cover.png

sketched-books.epub: ebook.html
	ebook-convert ebook.html sketched-books.epub --cover cover.png --authors "Sacha Chua" --language "English"

sketched-books.mobi: ebook.html
	ebook-convert ebook.html sketched-books.mobi --cover cover.png --authors "Sacha Chua" --language "English"

ebook.tex: ebook.org
	emacs --batch -l build.el ebook.org -f org-beamer-export-to-latex --kill

ebook.pdf: ebook.tex
	pdflatex ebook.tex
	cp ebook.pdf sketched-books.pdf
	rm ebook.pdf

And here’s a very simple build.el:

(require 'package)
(package-initialize)
(require 'ox-beamer)
(setq org-html-validation-link nil)
(setq org-export-with-section-numbers nil)
(setq backup-directory-alist '(("." . nil)))

This assumes I’ve already set up the environment by installing the latest Org from MELPA.

You can check out the index.org and ebook.org I use, too.

I’m not quite sure about the MOBI output yet. I have to test it on a Kindle, or in the app on my tablet. Most of the things display fine on my computer, though. Hooray!

Neat, huh? I want to get into the habit of making and also making it easy for me to update these things. You can check out the results at http://sketchedbooks.com/collection .

Someday I might even figure out how to use the Gumroad API to publish updated resources automatically. Wouldn’t that be neat? In the meantime, I’ll just have to replace them myself.

I like giving people the ability to choose which files to download. If I get annoyed with replacing multiple files, though, I might change this to one large ZIP that has the images, PDF, EPUB, and MOBI.

View the source on Github

Start your titles with a verb to make them stronger; or reflections on titles, filler phrases, and my life as a gerund

Instead of using a generic title (ex: Top 10 Ways to …), pick your strongest point and put that in the title as a clear recommendation.

Now that I’ve gotten that promised tip out of the way, here’s the reflection that prompted this post.

Many bloggers focus on improving their titles as a way to encourage people to click or share. Having repeatedly run into the limitations of my blog searches and index, I’ve been thinking about blog post titles as a way to make my blog posts more memorable – both in terms of retrieval (remembering what to look for) and recognition (recognizing it when I come across it).

That’s why many of the usual title-writing tips don’t appeal to me, even if they’re backed by A/B testing. List posts? A focus on new or exclusive information? Mysterious headlines? While writing a post called “10 New Emacs Productivity Tricks That Will Make Vim Users Hate You – #2 Will Save You Hours!” is tempting to consider as an April Fool’s Joke, that kind of title is useless for me when I’m trying to find things again. Any title generic enough to come out of a blog post title generator is too generic for me to remember.

Fortunately, there are plenty of role models on the Web when it comes to writing clear, specific blog post titles. Lifehacker somehow manages to do this well. Most of its posts start with a verb, even when linking to a post that doesn’t, and yet it doesn’t feel overbearing.

Here’s a sample of Lifehacker titles for posts that summarize and link to other posts (ignoring posts that were original guides, product links, or fully-reposted blog posts):

Lifehacker title Original post
Re-Read Old Books After a Few Years to Gain New Perspective How you know
Agree On a Special Signal So Your Colleagues Can Reach You On Vacation 11 Valuable Tips for Handling Emails While on Vacation
Find the Best Thrift Stores Near You Using Zillow and Google Maps How to Find the Best Thrift Stores in Your Area
Find a Hobby by Rekindling Your Childhood Passions 7 Strange Questions That Help You Find Your Life Purpose
Conduct a “Nighttime Audit” to Sleep Better How to Spend the Last 10 Minutes of Your Day
Get Your Ideas Out of Your Head to Start Improving Them 6 Lessons from Pixar that Will Set You Up for Success
Focus on Discipline More Than Motivation to Reach Financial Goals Forget Motivation, This is the Key to Achieving Your Goals This Year
Give Yourself a Creative Game Each Day to Boost Inspiration The Importance of Personal Projects
Fix Your Bluetooth Audio in Yosemite With This Terminal Command Commands to Make Yosemite Suck Less

Fascinating. Of the nine posts I looked at, all of them rewrote the titles from the original blog posts so that they started with a verb, making the titles more specific in the process. This makes sense in the context of it being a lifehack, of course. The concept has action at its core.

I like the new titles more. I can imagine that remembering and linking to the Lifehacker-style titles would be easier than linking to the original ones.

Most of my posts don’t quite feel like those, though. I noticed that most of my titles start with gerunds: thinking about, building, learning, exploring, experimenting. I think it’s because I write in the middle of things, while I’m figuring things out. I don’t feel comfortable telling people what they should do. I share my notes and let people come to their own conclusions. Starting a post with a verb seems to be too direct, as if I’m telling you to do something.

That said, filler phrases like “Thinking about…” aren’t particularly useful as part of a title, since the reflection is a given. But changing “Thinking about how to make better use of Yasnippet in my Emacs workflow” to “Save time with dynamic Yasnippets when typing frequently-used text in Emacs” doesn’t seem to accommodate the exploratory bits, although it could be a good follow-up post. Changing “Minimizing upward or downward skew in your sketchnotes” to “Minimize upward or downward skew in your sketchnotes” feels like I’m making a value judgment on skewed sketchnotes, when some people might like the fact that an upward skew tends to feel happy and optimistic.

So I use nouns or gerunds when reflecting (which is self-directed), and verbs when I’m trying to put together other-directed advice. This helps me differentiate the types of posts in my index and in my editorial calendar admin screen, and it also signals the difference to people as they browse. You might not be interested in my reflections and prefer to focus on tips, for example, or you might be tired of tips and want journal entries instead.

That works because those types of posts are generally quite separate. When I want to help someone learn a technique such as sketching quick ribbons, I don’t go on an extended tangent about how I learned how to do that or how I want to improve. When I’m thinking about how I can improve my delegation skills, I don’t expect someone to patiently go through all of that in search of three concrete tips to help them improve. I think that as I gain experience and become more opinionated (the latter probably being more related to this), I’ll write more advice/instruction posts, possibly linking to those personal-experience-and-reflection posts instead of going on internal tangents.

In this post, I’m experimenting with a verb title while doing extensive self-reflection. It feels a little odd, as if you started a conversation with someone and then proceeded to talk to yourself, idly musing out loud. You’ll have to tell me if I should never do that again, or if there’s a way to manage the balance. But it also feels odd to use my part of the conversation to tell you to do stuff, solely drawing on other people’s research or recommendations, without sharing my context so you can tell if something that makes sense for me might make sense for you. I figure there are plenty of other people out there who want to tell you what to do with your life, and I’m not completely fond of that approach anyway. And it also feels odd to natter away about my life like a self-absorbed ninny, making you do all the hard work of translating ideas into things that you can actually use. I still haven’t completely figured out how to make personal blogs more useful for other people.

Could I make an idea sandwich: summary and research at the top, personal reflection in the middle, call to action at the end? Maybe that could work.

Still, I want to do something with my titles so that I don’t end up with lots of “Thinking about …” and “Exploring …” and “Deciding between …” that blur in my memory. My ideal for these reflection posts, I think, would be a clear, concise summary of the key insight (perhaps saving it as an excerpt as well, if it doesn’t fit in the title). If I followed that up with an other-directed post with a crisp title that started with a verb, made the recommendation, brought in some research and observations, and linked to my reflection, that would give me a good, logical, memorable, useful chunk that I could share with other people.

Right. That makes sense to me. If I address you with a direct verb or “How to …”, I should deliver a post that requires minimal mental translation for you to get good tips out of it. If I clearly mark something as a reflection, you know what to expect. I tend to remember them as actions I decided to take (“The time I resolved to…”) or the particular new thing I came to understand. I can take a few minutes to update the titles and summaries accordingly, which could help me years later when I’m trying to make sense of things again.

In Buckminister’s somewhat strange book I Seem to Be a Verb (1970), he wrote:

I live on Earth at present, and I don’t know what I am. I know that I am not a category. I am not a thing—a noun. I seem to be a verb, an evolutionary process—an integral function of the universe.

A verb seems too definite for me. I’m a gerund in at least two senses, I think: reflexive, the way “I read” is an act but “reading” is a noun that lets us talk about itself; and in the process of doing, not done.

Do you write other-directed posts that offer advice or instruction? Consider lopping off “How to …” and “Top 10 ways to…”. Start with a verb and give one clear recommendation. Do you write self-directed reflections? See if you can harvest the ideas for other-directed posts, and perhaps invest a little time into making your posts easier for you to remember. Do you write a mix of both, and have you figured out a good flow? I’d love to hear what works for you.