To find this code, I searched ox-html.el for [. Eventually I found org-html-checkbox, which is directly called by org-html-format-list-item instead of being a function variable that you can change. So that meant I needed to override the behaviour of org-html-checkbox through defadvice. You can see above how I wrap advice around org-html-checkbox and replace the return value with my own function. For more about advice, read the Emacs Lisp Intro manual.
To find the hex codes for the UTF-8 characters, I searched Google for UTF-8 checkbox and found BALLOT BOX WITH CHECK. I used the hex code so that I didn’t have to worry about encoding issues. I tested it by updating one of my weekly reviews. Tada!
Learning on your own can be really hard. Once you get past the basics, there aren’t that many books or courses about what you’re interested in. It makes sense. It takes effort to make a book or course, and authors and teachers tend to prefer larger markets. As you gain experience, you need more specialized knowledge, and it can be hard to find existing packaged information or people who can give you good feedback. People around you might not know what you’re talking about, and you might not be able to find mentors in the same city. Even figuring out what you want to learn and in what order can be challenging, especially if you’re learning about the intersections of topics instead of just one topic. Here are some tips I’ve picked up for learning on your own:
Look for inspiration. Find people who are doing what you want to be doing. Ask yourself: What do you like about their work? What do they do differently? How can you learn from them? They might never write a book or teach a course–they might not even recognize that what they do is worth teaching others–but you can still learn from their example. You can learn by watching them, and you can even reach out and talk to them.
Review your work. Try to find examples where you’ve already done what you want to do, even if it was by accident. Ask yourself: What did you do well? What did you like about it? What was different? What can you improve on next time? Look for ways to deliberately practise the skills you want to develop.
Make your own maps. If you’re learning about something that doesn’t have a clear outline or curriculum, it’s easy to feel scattered and discouraged. Make your own map. List your questions, and keep track of your progress as you answer them. Figure out what the next steps are. You might be able to ask mentors to help you make a better map. Mentors can tell you if there are easier ways to learn something, or if there are related topics that you would find useful. Make your own curriculum so that you don’t feel lost.
2014-02-02 Learning on your own
If you’re learning about things on your own, you’ll probably need to come up with your own ways to practise what you’re learning so that it becomes part of the way you work. Instead of being intimidated by the size of what you want to learn, break it down into smaller skills that you can practise. Look for ways that you or other people have done it well, and plan your own exercises so that you can learn how to do well consistently. Deliberate practice is the key towards building confidence and skill. Think about how you can practise that skill in a way that gives you quick feedback on whether you’re doing it right or wrong. You might be able to check your work on your own, or this might be something a coach or mentor can help you with. Keep track of how you do on these exercises – it’s great to feel your progress.
If you’re having a hard time with the exercise you’ve come up with, break it down into smaller pieces and try working more slowly. Improve your accuracy and consistency before you improve your speed. If you find the exercise too easy, take the next step. Think about the results you’re getting and adjust the way you practice. Good luck!
2014-02-04 How to create your own exercises for deliberate practice during self-directed learning
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.)
Books tend to be better-organized and more in-depth, but these days, I get more current information and insights from blogs. Reading lots of blogs can take time, though. Worse, it’s easy to get distracted by the interesting links and ideas you’ll come across. Next thing you know, it’s two hours later and you haven’t even started working on your project.
Here are the tools and strategies I use to read blogs. I hope they help!
I subscribe to blogs I regularly read, and I read them using a feed reader. Some blogs are great for inspiration and serendipity. Other blogs are written by people I’d like to learn more about, and I don’t want them to disappear in my forgetfulness. Instead of subscribing by e-mail, I use a feed reader to organize the blogs I want to read in different folders, so I can prioritize which folder I want to read first.
You might not have come across feed readers yet, or you may already be using one without knowing what it’s called. Feed readers (also known as aggregators) are tools that go to all the blogs you’ve subscribed to and get a special version of the blog updates formatted so that computers can easily understand it. The tool then displays the information in a form you can easily read.
Many feed readers allow you to organize your subscriptions into folders. For example, I have an “AA Skill Development” folder for professional development blogs that I skim when I find myself with a moment of time. I add “AA” to the beginning of folders that I’d like to see first in the list, since the folders are alphabetically sorted. Organizing your subscriptions into folders is great because that allows you to quickly read through lots of similar topics together.
I read most blog posts on my phone, quickly paging through headlines and excerpts. I rarely read blogs when I’m at my computer. After all, I could be doing something more productive instead, and I don’t want to get distracted by the links. The Feedly app isgreat for this because it can synchronize across devices. Many feed readers even let you read while you’re offline, which is great for learning things when I’m on the subway. Lately I’ve been skimming through everything, newest posts first. It doesn’t take me a lot of time to do so, and it means that I don’t forget to read the folders down the list.
When I come across something I find interesting, I use the Save for later feature in Feedly. I can then follow up on it when I get back to my computer by checking my Saved for later folder. I usually save this for my weekly review. In fact, I have an If This Then That recipe that copies my saved items into Evernote, and I have an Emacs Lisp script that exports that list and makes it part of my weekly review. That’s probably the geekiest part of my setup, so don’t worry if that makes you gloss over. =)
You don’t have to read everything. You don’t even have to skim through everything. Feel free to use the Mark all as read feature, or to ignore the unread count.
Most feed readers can autodetect the feed for the site you want to subscribe to. For example, if you want to add this site to your Feedly, you can try putting in http://sachachua.com/blog and it should show you the recent posts. I write about a lot of different topics, so if you want, you can subscribe to just one category. For example, if you only want my learning-related posts, you can subscribe to http://sachachua.com/blog/category/learning/feed .
I like using the free Feedly reader, and there are many other options out there. I hope you find something that works for you!
Coming back to cold weather was not particularly fun, but I’m learning to deal with it. I’ve got the thermals, the sweaters, the jackets, the scarves… There’s no reason why I shouldn’t be able to figure out how to cope with winter. =) Anyway, here are some tips for people who are new to Canada or other cold places:
Other winter notes: My insulated winter boots have sprung a leak. I still have a pair of leather boots and a pair of rubber boots (in bright red!), so I think I’ll make it through this winter. I shopped around for a replacement pair this weekend and didn’t find anything I liked, despite the sales. I was thinking about whether I should get a pair for when these boots wear out, but I’ll probably move away from wearing insulated boots and move towards thick socks and hiking shoes or regular boots instead. It’s also a good time to see if I can repair the boots I have. Oh well!
Sacha Chua Yup, you can check out http://pages.sachachua.com/.emacs.d/Sacha.html - search for org-agenda-custom-commands and look at the entry for "b". Hmm, I should experiment with capturing more formal... – My current book workflow