Category Archives: writing

On this page:

Sketchnotes 2013 in print, yay!

Summary: You can now grab a print copy of Sketchnotes 2013 for $30 + shipping from CreateSpace.

2014-03-24 Sketchnotes 2013 in print, yay #publishing #packaging #createspace

2014-03-24 Sketchnotes 2013 in print, yay #publishing #packaging #createspace

I like organizing my sketches into collections so that people can flip through them easily. It’s a good archive too, just in case I lose files. I put together a PDF of my sketchnotes from 2012, and I recently put together one for my sketchnotes from 2013. For added flexibility, I started with a ZIP and shared Dropbox folder for Sketchnotes 2013.

Paul Klipp suggested that I look into CreateSpace as a way of making a paper version. CreateSpace is a print-on-demand publisher, so we can order copies one by one instead of stashing inventory. Paper is easier to flip through during casual moments, and it might be a good alternative. Besides, it’s handy as a personal backup, too. A lot of the sketchnotes are me thinking through stuff, so I’m not sure how useful they’ll be to other people, but you can check it out online for free to see anything is useful. =)

2014-03-24 17.15.56 2014-03-24 17.16.12

It turns out that CreateSpace’s pricing–even considering the cost of shipping–is cheaper than what it would take for me to get color prints at the local print shops, and the results are neatly bound and professional. My proof arrived today, and it looks decent. I had reduced my landscape sketches to a little less than half their size so that I could fit them two to a page. That makes reading easier because you don’t have to turn the page sideways. I was worried that the letters wouldn’t be readable, but they turned out fine. =D

End result: I can “back up” my sketches in a much more compact space, and you can get your own copy if you want. For comparison, here’s the stack of sketchbook pages I drew on and scanned.

2014-03-24 18.22.06

Sketchnotes 2013 ($30 + shipping)

Geekier details: LaTeX

I wanted to make a PDF collection, but I didn’t want to work with a gigantic Microsoft Word or Powerpoint file. I’d done that before with Stories From My Twenties and Sketchnotes 2012, and that was not fun. Anyway, I had folders of images to combine. At first, I tried using ImageMagick to tile the images into pairs and pad them with margins. That was pretty cool. Adobe Acrobat Standard allowed me to import the images and add page numbers. I created my own table of contents using Microsoft Excel, pasted that into Microsoft Word, and tweaked the numbers until they were correct. It was a tedious and error-prone process.

Marcin Borkowski suggested using LaTeX instead. It’s been years since I used LaTeX. I remember doing some of my papers in it, and they always looked so much better than anything I put together in Microsoft Word or OpenOffice. I didn’t want to deal with the potential hassle of setting up LaTeX under Windows or Cygwin. I’d gotten more used to using Vagrant and VirtualBox to run Linux-based virtual machines that shared folders with my Windows installation, and upgrading to a 1 TB drive meant that I had plenty of space.

One of the advantages of working with LaTeX is that it’s text-based and therefore easy to work with in Emacs. I wanted to break up the different sections into their own files. I started with a small category. That way, I could easily recompile a section of the PDF in order to figure out the right approach.

Because I was using Windows to look at the PDF, I often got annoyed by the preview pane file-locking that prevented me from deleting the file. I turned the preview pane off in Explorer and opened the PDF whenever I wanted to check it.

After looking up how to include images in LaTeX, I listed all the image files, redirected the output into a file, and used a keyboard macro to set up \includegraphics commands.

It’s a good thing I did that, because some of the files were facing the wrong way, and many of them were the wrong size. So I learned how to resize and rotate images like this:

\includegraphics[height=\textwidth,angle=90]{Business/2013-02-26 Creating value with social collaboration platforms}

A couple of notes:

  • \includegraphics displays filenames with spaces, which wasn’t what I wanted. Adding \usepackage{grffile} fixed it.
  • \includegraphics can’t deal with special characters like #. To be safe, I used M-x dired‘s editable mode (C-x C-q) to get rid of all the keywords I added to each filename for classification.

Since I had a lot of these commands, I figured it would be worth learning how to define my own command for them. LaTeX is like Emacs. You can define your own commands or override existing ones. This is great for making your code more manageable. For example, if I include the following definitions in my document preamble:

\newcommand{\sketch}[3][height=4.5in,width=\textwidth,keepaspectratio]{
  \addcontentsline{toc}{section}{#3}
  \includegraphics[#1]{#2/#3}\\
}
\newcommand{\sketchcw}[2]{
  \sketch[height=\textwidth,angle=270]{#1}{#2}
}
\newcommand{\sketchccw}[2]{
  \sketch[height=\textwidth,angle=90]{#1}{#2}
}

… that gave me new commands that I can use like this:

\sketchcw{Business}{2013-02-26 Creating value with social collaboration platforms}
\sketchccw{Business}{2013-03-04 New opportunities}
\sketch{Business}{2013-03-04 Sketchnotes of events}

I also wanted to include a table of contents that listed all the images, but I didn’t want to display captions since they would duplicate the title that’s already in the sketchnotes. At first, I tried to use captions and labels, but I found out that you can use \addcontentsline to adds lines to the table of contents without displaying anything in the text.

After I set up and successfully compiled a few files, I worked on creating a main document that combined everything. The subfiles package was straightforward to use.

The trickiest part was getting the chapter table of contents sorted out. In addition to having a main table of contents, I like having chapter-based tables of contents because that way, the list is closer to what you’re looking up. I eventually figured out how to use minitoc after much confusion with left-over minitoc data and chapters that were out of order. I ended up creating a Makefile to clean out all the auxiliary files and run pdflatex three or four times.

Here’s one of my early sketches trying to figure this out, back when I was using ImageMagick and Adobe Acrobat…

2014-02-27 How can I make it easy to print collections of my sketches #packaging #sharing

2014-02-27 How can I make it easy to print collections of my sketches #packaging #sharing

It’s great to be a geek!

More notes on managing a large blog archive: 17 things I do to handle 10+ years of blog posts

I’ve been thinking a lot about how to manage a large archive to encourage discovery and serendipity, and to make it easier to fish out articles so that I can send them to people. I started in 2001-ish and have more than 6,500 posts. There’s not a lot of information on how to manage a large archive. Most blogging-related advice focuses on helping people get started and get going. Few people have a large personal archive yet. I love coming across other bloggers who have been at this for more than ten years, because information architecture is fascinating. Here’s what I do, in case it gives you any ideas.

  1.  I set up Google Chrome quick searches for my blog, categories, and tags. This means I can quickly dig up blog posts if I remember roughly where they are. (Gear > Settings > Search > Manage Search Engines):
    • Blog (b): https://www.google.ca/search?q=site%3Asachachua.com+%s
    • Blog category (bc): http://sachachua.com/blog/category/%s
    • Blog tag (bt): http://sachachua.com/blog/tag/%s
  2. I create pages with additional notes and lists of content. I use either Display Posts Shortcode or WP Views, depending on what I need. See the Emacs page as an example.
  3. I’ve started using Organize Series to set up trails through my content. It’s more convenient than manually defining links, and it allows people to page through the posts in order too. Read my notes to find examples. I’m also working on maps, outlines, and overviews.
  4. I’ve also started packaging resources into PDFs and e-books. It makes sense to organize things in a more convenient form.
  5. I converted all the categories with fewer than ten entries to tags. Categories can get unwieldy when you create them organically, so I use categories for main topics and tags for other keywords that might graduate to become categories someday. I think I used Categories to Tags Converter or Taxonomy Converter for this. Hah! Similar Posts reminded me that I used Term Management Tools. Awesome.
  6. I manually maintain a more detailed categorical index at sach.ac/index. This makes it easier for me to see when many blog posts are piling up in a category, and to organize them more logically.
  7. I set up short URLs for frequently-mentioned posts. The Redirection plugin does a decent job at this. For example, people often ask me about the tools I use to draw, and it’s great to just be able to type in http://sach.ac/sketchtools as an answer.
  8. I post weekly and monthly reviews. The weekly review includes links to that week’s blog posts, and the monthly review includes a categorized list. I’ve also set up daily, weekly, and monthly subscriptions based on the RSS feeds. This is probably overkill (more choices = lower subscriptions), but I want to give people options for how frequently they want updates. The weekly and monthly reviews are also helpful for me in terms of quickly getting a sense of the passage of time.
  9. I use Similar Posts to recommend other things people might be interested in. There are a number of similar plugins, so try different ones to see which one you like the most. I tried nRelate and the one from Zemanta, but I wasn’t happy with the way those looked, so I’m back to plain text.
  10. I show recent comments. People often comment on really old posts, and this is a great way for other people to discover them.
  11. I use post titles in my next/previous navigation, and I labelled them “Older” and “Newer”. I think they’re more interesting than
  12. I customized my theme pages to make it easier to skim through posts or get them in bulk. For example, http://sachachua.com/blog/2014/02 lists all the posts for February. http://sachachua.com/blog/2014/?bulk=1 puts all the posts together so that I can copy and paste it into a Microsoft Word file. http://sachachua.com/blog/2014/?org=1 puts it in a special list form so that I can paste it into Org Mode in Emacs. You can also pass the number of posts to a category page: http://sachachua.com/blog/category/drawing/?posts_per_page=-1 displays all the posts instead of paginating them. These tweaks make it easier for me to copy information, too.
  13. I give people the option to browse oldest posts first. Sometimes people prefer starting from the beginning, so I’ve added a link that switches the current view around.
  14. I have an “On this day” widget. Sometimes I notice interesting things in it. I used to put it at the end of a post, but I moved it to the sidebar to make the main column cleaner.
  15. For fun, I have a link that goes to a random post. I used to display random post titles in the sidebar, which might be an interesting approach to return to.
  16. I back up to many different places. I mirror my site as a development environment. I back up the database and the files to another web server and to my computer, and I duplicate the disk image with Linode too. I should set up incremental backups so that it’s easier to go back in time, just in case.
  17. I rated my posts and archived my favourite ones as a PDF so that I’ll still have them even if I mess up my database. Besides, it was a good excuse to read ten years of posts again.

Hope that gives you some ideas for things to experiment with! I’m working on organizing more blog posts into trails and e-books. I’m also getting better at planning what I want to write about and learn. If you’re curious about any of the techniques I use or you want to bounce around ideas, feel free to e-mail me at [email protected] or set up a chat.

Do you have a large blog? How do you manage it?

Reflections on infopreneurship

There’s a lot of information on how you can build an online business by selling what you know. Many people are looking for that dream. It feels a little weird to me, and I want to figure out why. I guess one of the things that rubs me the wrong way is that a lot of people talk about becoming an expert in some crowded topic, and building an audience somehow. I don’t want an audience. I don’t want students. I want peers and confederates: people who learn, act, reflect, and share.

2014-02-14 Reflections on infopreneurship and alternatives

2014-02-14 Reflections on infopreneurship and alternatives

Another thing that makes me uncomfortable is that there seems to be very little expectation of action. There’s a lot of talk about it. But when I go and follow up with people on the results of the advice I applied from them, they’re boggled that I actually did something. One person I talked to said that 80% of the people he talked to don’t end up doing anything. 20% is still a good number, but still…  Steve Salerno wrote in Sham: How the Self-Help Movement Made America Helpless that the people who buy new self-help books tend to be people who bought a similar self-help book in the past 18 months. I don’t want to give people something that just makes them feel like they’ve made progress instead of helping them actually do things.

I think part of my hesitation comes from this: People get stuck for lots of different reasons, but it’s rarely for lack of reading. I don’t want to pitch information as the magic pill, the silver bullet, the shortcut to making things happen.

When I read, I skip platitudes but dig into reflections and lessons learned. I like processes and workflows. I want what I share to be similarly useful. The stuff that helps me get unstuck tends to result in thoughts like this:

  • “Oh! That’s the name of what I’m looking for. Now I can dig into the details.”
  • “Hmm, what I’m dealing with turns out to be fairly common. I can try what other people have done.”
  • “Oh, I see, I was missing that particular piece. Let me try this now.”
  • “Interesting question! Let me explore that…”
  • “Okay, that’s less intimidating than I thought. I should just go for it.”
  • “I had no idea you could do that! Oooh…”

What can I write or draw to help people get those moments? How do I help people get unstuck – or better yet, how can I help them accelerate or expand their learning? And since I can code and tinker and dream… What can I make? Ideas are one thing, but tools are another. I’ll keep an eye out for places where people are consistently getting stuck, and I’ll see which ones lend themselves to automation.

2014-02-14 Building systems to help people do things

2014-02-14 Building systems to help people do things

As I explore packaging and publishing more, I want to focus on stuff that people can’t find in a gazillion other blogs and e-books out there. Keep me honest. =) I like making things free/pay-what-you-want, since it helps me act from abundance, widen the conversation, and make room for people’s generosity. I’ll also share the processes and tools I’m building for myself. If you find them interesting, tell me, and maybe we can find ways to tweak and expand them to accommodate your idiosyncrasies as well as mine. I like the conversations that grow out of this, too.

Some of my technical role models have published books (both self-published and traditional). I can see how that saves a lot of people time and helps people learn. They work on open source projects and commercial systems too. I think that’s the sort of information work I want: stuff that helps people do things.

Hmm… Aha! Maybe that’s it. If I focus on helping fellow geeks solve problems or try interesting things (mostly tech, some lifestyle?), then I don’t have to worry as much about wasting people’s attention. We’re used to trying things out and testing them against our own experience, and we’re used to telling people “Hey, that didn’t quite work for me” or “That saved me a few hours of figuring things out! Here’s something to make it even better.” =)

2014-02-24 Aha, a plan for the things I want to write #experiment

2014-02-24 Aha, a plan for the things I want to write #experiment

(No offense to life coaches, motivational speakers, and self-help authors. Hey, if it works for you, great. =) I don’t have the experience to give good, well-tested advice in that area yet.)

Technical guides, I think. My long-postponed book about Emacs. Short guides about Org Mode or automation or Evernote or information management. There’s a lot to write. These aren’t books people read for inspiration and the vague desire to do something someday; they address what people want to improve now. (Well, maybe Emacs is a little on the inspirational side. ;) )

It’s easy for me to connect with people who are already travelling similar paths. I can share my notes. I can reach out and ask questions. What about helping people who are just starting down those paths? Maybe that’s where packaging what I know can be useful, especially if I can help people accelerate their learning and diverge to follow their own questions. My selfish desire is to learn from other people’s perspectives. I don’t want to make people dependent on me, the way that people seem to become fans of one motivational speaker or another. I want people to learn from what I’ve learned, but I also want them to translate it to their contexts, test it against their lives, and add their own insights. I’m happy to spend extra time helping beginners who do stuff, think about it, and then go on to ask different questions.

2014-02-09 How do I want to manage my learn-share pipeline

2014-02-09 How do I want to manage my learn-share pipeline

So, what would the processes look like if I figured this out? I’d have a good balance of thinking, learning, doing, and sharing. I’d be able to work top-down from outlines, anticipating the questions people might have. I could work bottom-up from questions and blog posts, too. I might not notice that I have enough to publish, so I could establish triggers to check whether enough has accumulated that it needs to be chunked at a higher level of abstraction: Q&A or sketches into blog posts, blog posts into series, series into short books, short books into longer ones. I’d harvest all the generally useful Q&A from e-mail and conversations to make sure they’re captured in the pipeline somewhere, even if it’s an item in my Someday list.

Onward!

A No Excuses Guide to Blogging (PDF, EPUB, MOBI – free!); also, notes on publishing

This entry is part 1 of 19 in the series A No-Excuses Guide to Blogging

First, a quick announcement: A No-Excuses Guide to Blogging is now available as a free/pay-what-you-want e-book so that you can work your way through your excuses without having to click through lots of blog posts. =)

Mock-up by Ramon Williamson


Mock-up by Ramon Williamson

The cover I made for Amazon

The cover I made for Amazon

The PDF looks prettiest if you’re reading it on your computer or tablet, and the EPUB/MOBI version is handy for other e-readers. You get all three (and any future updates) if you grab it from http://sachachua.com/no-excuses-blogging, or you can get the MOBI version from the Kindle store (currently $0.99, but eventually they’ll price-match it to $0). The book is under Creative Commons Attribution, so feel free to share it with other people. =)

UPDATE 2014-02-13: Here’s a one-page summary!

2014-02-13 A No-Excuses Guide to Blogging - Summary of 10 blogging excuses and how to work around them

2014-02-13 A No-Excuses Guide to Blogging – Summary of 10 blogging excuses and how to work around them

 

- Behind the scenes stuff! – 

So this was about 8 hours of packaging after I’d identified the topics and asked an assistant to compile all the blog posts in a Word document. I edited the text to make it fit better in a collection, fiddled with the graphics, added more sketches, tweaked the layout some more, fought with section headers, and eventually created a PDF that I was reasonably happy with. I contacted a bunch of people on Fiverr about converting the DOCX into EPUB and MOBI. While waiting for a response, I decided to try doing it myself. It took me some time to clean up the messy HTML, but I’m reasonably happy with how the EPUB worked out. I had to tweak the EPUB table of contents in order to get it to pass the validator used by Lulu, but eventually I got it worked out with Calibre and Sigil. The MOBI was a straight conversion from the EPUB, although I wonder if I can get the background colour to be white…

2014-02-05 Notes on publishing

2014-02-05 Notes on publishing

So that was interesting and useful, and it would be good to do more. Here are some ideas for other “No Excuses”-type guides I might put together. Maybe self-directed learning and delegation, actually, since other people are covering the sketchnoting bit quite well.

2014-02-06 What other excuses can I collect and work around

2014-02-06 What other excuses can I collect and work around

There’s also this list of other book ideas, Thinking with Emacs, Tracking Your Time, Accelerating Your Learning with Sketchnotes, and this big outline. Lots to do. Looking forward to figuring out how I can get more of these out the door. =)

In the meantime… tada! http://sach.ac/no-excuses-blogging

Series NavigationWrite about what you don’t know: 5 tips to help you do research for your blog »

How to develop your ideas into blog posts

This entry is part 13 of 19 in the series A No-Excuses Guide to Blogging

Do you find it easy to come up with lots of ideas for blog posts, but then find it difficult to sit down and actually write them–or spend hours drafting, only to decide that it’s not quite ready for posting?

I know what that’s like. On the subway, I jot a few notes for a post I want to write. At home, I add more ideas to my outline. Sometimes when I look at those notes, I think, “What on earth is this about?” Other times, I write a paragraph or two, and then my attention wanders. Over the years, I’ve gotten a lot better at getting posts out there. I still have more ideas than I can write, but at least a few of them make it into my blog! Here’s what works for me, and I hope it works for you too.

Capture your ideas. Write them down somewhere: a text file, an Evernote notebook, a piece of paper, whatever fits the way you work. You don’t have to write everything down, but it helps to have a list of ideas when you sit down to write. I use Evernote to take quick notes on my phone, and I use Org Mode for Emacs for my outline.

“Oh no! Now I have this huge list of unfinished ideas!” Don’t be intimidated. Think of it like a buffet – you can choose what you want, but it doesn’t mean that you have to finish everything.

Pick one idea and turn it into a question. Pick the idea that you’re most curious about, perhaps, or something that you’re learning. Turn it into a question so that you have a focus for your writing and you know when you’ve answered it. Questions help you keep both your perspective and your reader’s perspective in mind. Remembering your question will help you bring your focus back to it if your attention wanders. Remembering your readers’ potential question will help you empathize with them and write for them.

Break that question down into smaller questions until you can actually answer it in one sitting. For example: “How can you blog more?” is too big a question. In this post, I want to focus on just “How do you get past having lots of ideas that you don’t turn into blog posts?” Make the question as small as you can. You can always write another blog post answering the next question, and the next, and the next.

When you find yourself getting stuck, wrap up there. That probably means that your question was too big to begin with. Break it down even further. Figure out the question that your blog post answers, and revise your post a little so that it makes sense. Post. You can follow up with a better answer later. You can build on your past posts. Don’t wait until it’s complete. Post along the way.

I often run into this problem while writing technical posts. I start with “How do you do ABC?”… and get stuck halfway because of a bug or something I don’t understand. Then I turn my post into “Trouble-shooting XYZ” with my rough notes of how I’m figuring things out. I’d rather have written a complete guide, of course, but mistakes and false starts and rough notes are also useful in themselves.

Don’t think that you have to know everything and write everything perfectly the first time around. In fact, blogging can be more interesting and more useful when you do it as part of your journey.

Perfectionist? Take a close look at that anxiety. See if you can figure out what the root of that is. Is it useful for you, or is it getting in your way? There’s an advantage to being outwardly polished, yes, but there’s also an advantage to learning quickly and building relationships. One of the tips I picked up from the book Decisive: How to Make Better Choices in Life and Work (Heath and Heath, 2013) was the idea of testing the stakes. Make a few small, deliberate mistakes. Ooch your way to better confidence. (See page 138 if you want more details.)

Tell me if this helps, or if you’re still getting stuck. More blogging excuse-busters here!

Series Navigation« Dealing with feeling scattered as a writer4 steps to a better blog by planning your goals and post types »

A no-excuses guide to blogging

UPDATE 2014-02-05: Download the PDF/EPUB/MOBI: A No-Excuses Guide to Blogging (free, pay what you want)

What’s getting in your way when it comes to writing?

2014-01-31 Getting good ideas out of your head - a path to publishing

2014-01-31 Getting good ideas out of your head – a path to publishing

Here are even more excuses, and some tips for dealing with them. =)

Excuse: “I don’t know what to write about.”
Write about what you don’t know.
Pay attention to what you’re learning.
Figure out what you think.
Ask for feedback.
Deal with writer’s block
Find tons of topics
Excuse: “There’s so much I can’t write about.”
Focus on what you can’t help but sharing.
Excuse: “But I’m not an expert yet!”
Share while you learn
Excuse: “I don’t want to be wrong.”
Test what you know by sharing
Excuse: “I feel so scattered and distracted.”
Don’t worry about your strategy
It’s okay to write about different things
Plan, organize, write, improve
Excuse: “I have all these ideas, but I never finish posts…”
Turn your ideas into small questions, then answer those.
Excuse: “I don’t feel like I’m making progress towards my goals.”
Be clear about your goals and possible approaches.
Excuse: “It takes too much time to write.”
Make sharing part of the way you work.
Excuse: “I’m too tired to write.”
Figure out what you can write better when you’re tired.
Excuse: “No one’s going to read it anyway.”
Focus on selfish benefits.
Get other people to read your posts.

See also other tips for new bloggers, and other posts related to blogging and writing. (Plus this list of WordPress plugins I use, if you’re curious about tech!)

Feel free to comment or email with more excuses and tips!