Tagging links: a hint

One of the more popular classes of productivity app is the social bookmarking app.  The principle behind sites like delicious, diigo, Google bookmarks, etc. is that a group of people will tend to reuse the same (or similar) bookmarks for similar items thus leadings, eventually, to a self-organizing collection of links.

Whether the hypothesis is a good one is, for my purposes here, irrelevant. (Personally, I think it is false because too many people seem unable to identify key and rather obvious tags associated with relatively obvious web resources.  But that's another story.)  These sites are also very useful for individuals simply trying to keep track of web resources for themselves.  I used to have a home-made system that treated keywords and tags as the same, which seemed to lower the number of tags one actually needed.  (I've not kept that system up just because I haven't time to nurse the code.)  Still, I find that existent systems are good enough - you probably will too.

But the question remains, how does one use tags in a sensible way?  This is a broad question that I don't really want to get into because it requires one to eventually call forth the cumulative knowledge of the library sciences with respect to categorizing resources.  And I know just enough to know that I don't know enough about that to comment intelligently.

There is one small "trick," though, that I've developed over the years, and that seems to work quite well for me.  It is this trick I'd like to share.

The trick involves trading off two goals: minimizing the number of tags one must remember and apply to a given resource; and capturing sufficient meta-data to be able to efficiently search for resources later.  I'll show the trick with and example.

Let's say you want to tag a resource as relating to decision making.  Depending on which site you use the syntax will vary, but most of the good sites allow multi-tag words or some approximation thereof.  I'll use double-quote to denote a multi-word tag, and I'll italicize tags to set them off from surrounding text.

There's three general techniques by which you can tag that resource.

1. decisionmaking - jam multi-word tags into a single word, which has the merit of reducing the extra characters (underscores, spaces, quotes, etc.), but hurts readability.  And what about makingdecisions?  Does that count?
2. decision-making or decision_making or "decision making" - You can separate words with special characters.  Some systems let you use hyphens; others support the use of double quotes to group multi-word tags.  I like hyphens because I don't have to hit the shift key to get one.  Other systems only allow underscores to join multi-word tags.  I find that annoying, but the underscore is a time-honoured mechanism for forming multi-word variable names in many computer languages - and since many of these systems started as some programmer's pet project…. Well, you know.
   Finally, some systems, like diigo, separate all tags with commas and allow spaces in tags.  This is perhaps the best, most natural, and efficient way of specifying multi-word tags.  That's one of the reasons why I have for a long time now used diigo.
3. decision and making - The last technique is perhaps a little counter-intuitive, but this is in fact my trick: treat each word in a multi-word tag as a separate tag.

Why on earth would you treat a multi-word tag as a whole bunch of tags?  Doesn't that break the semantics of the single, multi-word tag?

Well, yes it does, on the surface.  But I think that's a result of limiting your thinking to just what tags are most appropriate in some objective way.  Rather, I think we need to think of how you (and possibly others) might search for resources based on those tags.

So, what simpler way is there to search for something than just typing all the tags as separate words?  And what is most likely to catch related resources that might also interest you?  I think it's the single-word tag approach.  It's also pretty efficient in the long run.

For example, if you search for decision in a collection tagged as I suggest, you'll find all the resources tagged with that term, including those tagged with decision and making.  On the other hand, if you had treated decision making as a single tag, your search for decision wouldn't find them.  If you don't know that decision making is a single tag, then you might not find anything useful.

Many systems will show you a list of tags that occur with the tag for which you're searching.  So a search for decision will show, among other related tags, making.  Those systems will also show you other related tags, some of which may trigger new ideas.

This means that what you're really doing is constructing an implicit taxonomy of terms, where, in this case, decision is the most general term, and decision making is an item under the taxonomic tree for decision.  And it all happens naturally without any effort on your part.

So, as far as I can tell, treating multi-word tags as lists of single word tags is one of the easiest ways to enter tags, one of the most natural ways to search tags, and self-constructs a taxonomy of meta-data along the way.

Win-win-win, right?

Updated iPhone Task Manager Chart

I maintain a comparison chart of iPhone task management apps.  It's not very big yet, but I'm working on it.

I've updated the ratings of all apps currently in the chart.

I've also changed the presentation.  I've also colour-coded the values in the chart, so its easier to get an overall sense how the apps compare.  Red is "bad," yellow is "medium," and green is "good."  This is, of course, all based on my analysis.  Your milage may vary.

I note with interest that Taska seems to be the best, except for the bugs that seem to keep messing it up.  Too bad there hasn't been any activity on that app since Sep 2010.

Zotero: maintaining online bibliographies

Zotero is a bibliographic application developed at George Mason University, and it lets you manage, share, and export bibliographic information on the internet and locally on all your computers.  It's not the only package of its kind, but I think it's the best of the lot.



Zotero started life, and still works as, a browser plugin for Firefox.  It's very clever because it recognizes (most) web pages that contain citable documents, and lets you add that resource to your zotero library with one click.  You can of course add items manually if you want, and if you have a PDF or other file that contains a citable work, you can load it into the zotero plugin with drag-and-drop, and then have zotero scan it and search the internet for the bibliographic information to match it.  You can also tag any resource however you like, to make searching easier and faster.

You can create collections of resources and share them with other people.  This is great for students who are working on team projects, and also for researchers and academics who want to share resources with their students and colleagues.

And of course, you can export selected items in formats consistent with a variety of document processing packages, so you can largely automate the construction of the bibliographies in your own publications.

The one big problem with zotero used to be that it only worked with Firefox.  Many people had complained about this but its developers were adamant in not wanting to support different versions for different browsers.  As a Google Chrome user, I really found it annoying to have to keep Firefox open just for the sake of zotero.

But then they came up with a novel solution: create a standalone version that doesn't require a browser, and just write tiny, little plugins for the browsers that talk to the standalone version.  Granted, the standalone version is still in beta, but I've been using it regularly for quite some time and it seems to work just fine, almost all the time.  Occasionally, it has difficulty accessing the zotero servers - but that is quite rare.

There's a lot of useful information about zotero on their website, and I would encourage you to consider it if you're looking for a web-enabled way to manage your bibliographic information.

A great list of lessons

I know I took a shot at Leo Babauta last time, but it's important to remember that everyone makes mistakes.  Maybe I'm wrong; maybe he is.  Whatever.  I can say that there's some things that he and I do agree on.

Leo compiled a great list of "life lessons" that I would encourage everyone to read and adopt as rules to live by.  They distill in words far clearer than anything I've come up with, some ideas that I've had myself but couldn't quite verbalize.

I'd suggest only one modification, to Leo's first lesson about always being willing to apologize.  I don't believe in apologies.  An apology accepted is just permission to make the same mistake again.  And an apology denied is, well, useless.  Don't apologize. Instead, explain that you understand what you did wrong, and that you'll do your best to learn from the mistake.

I would note also that Leo's lessons seem to be good principles to achieve what I call balance. Balance is about finding that sweet-spot in life where you've got what you need, just enough to be good and happy, doing things that matter, with a minimum of stress.

I know what I'm going to do: build Leo's lessons into my own rulebook.

The myth of the myth of discipline

Normally, I have high praise for Leo Babauta's blog Zen Habits. However, I came across his page on the myth of discipline.  I don't get this page, because while arguing against "discipline," Babauta keeps talking about how to make habits.

And if you look up the word "discipline" and "self-discipline," you'll find that the ability to form habits is pretty much what discipline is.  It's a bit confusing.  Babauta is usually quite insightful.  That he didn't bother to study the dictionary definitions of discipline is atypical.

In point of fact, and using words as they are generally defined in English, discipline is just self-control based on a consistent system of rules.  So the best way to get discipline is to build habits.  And that's just how it is.

Of course, anyone can make mistakes, and this doesn't diminish the general validity of Zen Habits.  I guess the real lesson here is to remember to be flexible and adaptable, because one can never tell where a problem will come from, but come they will.

Chrome extension for Google Tasks

Google recently released a long-awaited API for Tasks.  They also immediately made available, code and all, an extension for Chrome that lets you access Tasks via a toolbar button.  This is great news for people who use Tasks.  (Previously, you'd have to have Tasks open in a window or tab, or access it via Gmail.)

A particularly cool feature of the extension is that you can add a task in two interesting ways:

1. you can just type t your new task in the Omnibar, no matter what web page you're on, and the task will be created; or
2. you can highlight text on any web page, right-click, and add that text to a new task.

This is good news for minimalists like me.  I'm going to have to seriously reconsider Tasks for my own task management system.

Google Tasks finally gets an API

Google finally announced on 11 May that they've published an API - an application programming interface - for its Google Tasks app.  Gtasks, as it's sometimes known, is a minimalist take on task management that I've written about before.  If you don't need projects, and contexts, and priorities, and stars and fancy stuff like that, you should look at Gtasks.  There are gtask apps for every kind of mobile device I can think of, and it links to Gmail and to Gcal.

An API is a standard way for programs to access other programs.  So for all of those people who write, say, iPhone apps that interact with web services, APIs are absolutely essential.

Gtasks has been around for a while now, and by far the most requested feature for the app was an API.  Since it was a long time coming, several programmers managed to figure out how to get their apps to talk to gtasks on their own - thankless task at the best of times.

Those days are, thankfully, over.

I predict there'll be a flurry of activity, especially in the mobile app world, as extant and new task management apps are written to take advantage of the new gtasks API, followed by a flurry of new products and apps to help us get things done fast and well.

I will keep an eye out for developments and post them here as quickly as I can.

Orgmode: productivity geek heaven

Orgmode, or just org, is an add-on for the venerable emacs editor that manages your tasks, builds your daily agenda, builds websites, outlines notes, help one keep a journal, tracks how long you spend on a task, and probably walks your dog and makes great julienned fries. Unfortunately, you have to be a bit of a geek to really appreciate it.


Don't get me wrong: I've got nothing against geeks, being one myself. Indeed, I think geeks rule - literally. I think we wouldn't be anywhere near as advanced as we are if it weren't for geeks, and I'm very satisfied to self-identify with the geekery. We might not be pretty or politically correct, but we do get shit done.

Still, geeks are not in large supply, so this productivity tool may not be to everyone's liking. But given that org is free and open sourced, and that it does damned near everything, it is very worthy of mention here.

For those who don't know emacs: it's the mother of all text editors. Much older than the Web, emacs is really a double-precision floating point dialect of the Lisp programming langauge, with a plain text interface, that happens to manipulate strings of text really well.  Some people have even compared it favorably with operating systems like Windoze and Linux.  (Well, anything compares favourably to Windoze....) It seems nearly infinitely flexible because it is its own programming language; an emacs program can load chunks of itself while it's running, thus changing its behaviour on the fly; it can even output its own source code.  Emacs works in modes, each of which is targeted at a specific type of task.  While emacs is best known as a programmer's tool, it can be taught to do nearly anything by just loading up the right mode.

Org-mode, as the name implies, is "just" one more of emacs's modes - about 85,000 lines of it. Originally designed written by Carsten Dominik, org recognizes certain special but not cryptic combinations of characters as specific types of information, and let's you do a number of interesting things with them.  You can see a number of screenshots of what org looks like here.

Typically, org is enabled on any file that ends with ".org" so you can create as many "org files" as you like, and the emacs editor will keep track of them, enabling org any time you open one of them.

One of the basic structures in org is the headline, a line of text that starts with some asterisks followed by a space. Text after a headline is treated as belonging to the headline. It's as if the headline were a section heading and the text below were the body of that section. Org understands subsectioning based on the number of asterisks that start a headline; the more asterisks, the deeper the level of the section. Text that goes with a headline is automatically visually indented to line up with the headline itself.  I say "visually" because, like real word processors, org recognizes that format is not content and rearranges text to fit nicely on the screen without altering the file itself.  (Of course, you can get org to embed the formatting directly into the file, but if you tend to transfer content from org into other applications, like blogs, then you don't want your content to carry all of org's formatting with you when you move it out of org.)

Org lets you hide the chunks themselves leaving only the headlines visible. This means you can use it as an outliner or what is sometimes called a folding editor.  You can lay out a long document by starting only with headings, then go back and work on the document one heading at a time, hiding all the others and focusing only on the one on which you want to work.  Indeed, in this regard, org has been compared favourably to apps like WriteRoom, especially because org and emacs are both free.

If the first word after the asterisks in a headline is TODO, org recognizes the headline as a task.   When you complete a task, you change its state to DONE, after which the task will no longer appear in your agenda (described below).  You can assign start dates, due dates, and priorities to these tasks.  Since a task is a headline, you can write as much as you want after the headline to describe the nature of the task, and then fold it away so it doesn't clutter up the screen.  Also, a subtask is simply defined as a sub-headline starting with one of the magic task keywords.

Org can then generate an agenda for you: a list of tasks according to deadline, priority, etc. and lay it all out for you in a easy to read, if somewhat unaesthetic, form.  Working on the agenda automatically works on whatever files were used to build the agenda, so you don't have to worry about not syncing the agenda with the other org files.  Of course, not all your org files need contribute to your agenda.  You can tell emacs which of your org files are those you want it to manage within the org agenda.

Orgmode agendas are dynamically constructed summaries of appointments, tasks, and all kinds of other things. You can even create your own combined agendas. Indeed, you can even define your own set of task status labels. The default list includes only TODO and DONE; I have TODO, WAIT, ACTIVE, DONE, and CANCELLED.  You can even define alternative sequences of task keywords, each representing a different possible workflow.  Besides the sequence I noted above, I have a separate sequence for "bugs" (OPEN, WIP, PAUSE, and CLOSED), and for projects (PROJECT and COMPLETED).  You can associate a shortcut key with each keyword, so changing the status of a task can be as short as one keystroke and never more than three.

This just scratches the surface of what org can do.  It can export its contents in all kinds of formats, including HTML, which means that you can publish your org pages to a website.  Not that you'd want your agenda published for the world to see, but since org includes outlining capabilities, you can literally create websites using it.  You can attach files, create links between different parts of different files, and link to images (such that when published to the web, the resulting web pages will have the images embedded in them).  Of course, all kinds of web linking is also possible; for instance, just pasting a URL into an org file automatically turns the text of the URL into a link to the corresponding web resource.

I've been using it for only a few months but I'm still exploring its functionality.  A(nother) nice thing about org is that you don't need to know all of it to use just part of it.  The functionality is very nicely compartmentalized, so you only need to learn as much of it as you need to use.  But be forewarned - once you get into it, you may want to learn more of it than you first thought.  Also, you may set up your org files in a way that makes functionality you haven't yet discovered harder to use because it doesn't "fit" with the way you work.

Of course, nothing is perfect, and there are some irritants in org (largely arising from emacs itself).

Emacs was born in a time before computer mice, even before the numeric keypads and function keys on your keyboard.  All that its original developers had at their disposal was the conventional keyboard.  So most commands involve holding the control key, or the escape, or meta, or opt, or whatever other special keys that don't print characters might be.  This means that some commands in org are composed of keystrokes that might seem bizarre to those unacquainted with emacs.  For instance, the three keystroke sequence control-c control-x control-e is how you get org to update the "effort" (i.e. number of hours needed) to complete a task that is currently being clocked.  Even though I've been using emacs for more than 20 years myself, there are days when I swear my hands cramp up from typing all those wonky keystrokes.

Another problem is that the documentation is not geared to the org beginner.  And if you're new to emacs generally, then heaven help you.  What's needed to make org really popular is a manual that anyone can use successfully.

One last major complaint I have about org is that the iPhone app for it, MobileOrg, requires you to sync by performing four separate manual operations.  Assuming you've set up org on a real computer to do remote syncing with MobileOrg, and configured the app properly (neither of which is a trivial task), you then have to manually push the content of your real org installation, then manually pull it into your iPhone.  Then, when you want to sync everything back to your main computer, you have to manually push from the iPhone and manually pull it all into your real computer.

Now, the iPhone app is quite new, but - really! - this is not how it should work.  For example: I sync my org files over all my computers using Dropbox.  Allowing the occasional and brief delay for Dropbox to work its magic, my org files are automatically synced everywhere.  And I know there are many iPhone apps that automatically sync to Dropbox.

Why can't they do the same thing with MobileOrg?

In any case, here's the bottom line.  Org for emacs is a fantastic productivity app that will only get better with time - if you can understand it.

Keyboard shortcuts in Chrome

Keyboard shortcuts can really speed you up, and help stop you from being distracted by having to reach for the mouse and then back to the keyboard.  Here's some extensions for Google Chrome that give you configurable shortcuts.



I find that moving my hand off my computer's keyboard to use the mouse is a supreme distraction.  Maybe it's just that I got used to computers before mice were ubiquitous - i.e. maybe I'm just old - but I find that having to move my hand back from the mouse to the keyboard breaks my concentration just enough to be supremely irritating - like a small round stone in one's shoe: it's not painful, but it is distracting.

So I love keyboard shortcuts, keystrokes that equate to mouse actions, menu selections, etc.  With a good set of shortcuts - and a little time to get used to them - one's hands can fly across the keyboard.  And more importantly, I find my concentration is unbroken because I'm not having to move my hand to the mouse and then back to the keyboard.

I pretty much use only Google Chrome these days, and I was getting more and more frustrated with the typical mouse-oriented interactions, so I set about looking for a Chrome extension that would give me some control over the keyboard.

It took longer than I thought to find something reasonable, so I thought I'd share the fruits of my labour.

My first discovery was the aptly named Shortcut Manager.  It offers a nice interface in which you can enter any keystroke and bind it to one of many, many actions.  However, it doesn't work very well.  For one thing, it misunderstood some keystrokes (e.g. the Apple Command key - I use only Macs - was interpreted as three Escape characters).  Even worse, though, is that it messed up the javascript in the browser so that I couldn't use buttons in the WYSIWYG editor at wordpress.  That's a showstopper.

Then I noticed that the extension hadn't been updated since December 2009.  That probably explains the bugs - Chrome continued to change, but the extension didn't.  Indeed, I'd wager that Shortcut Manager is dead.

So, back to the drawing board.

Next up is Vimium.  This extension creates a set of default shortcuts that are reminiscent of the vim text editor, which has two modes - a command mode (cursor movement, opening lines, deleting words, etc.) and an input mode (where keys insert their characters into the text).  Vim is based on vi, one of the original Unix text editors, which existed before computer mice, even before function keys and numeric keypads.

Currently, I use Vimium, and it seems to work fine.  '?' brings up a summary of the shortcuts, which is great for users still getting used to it.  Scrolling left, down, up, and right are bound to h, j, k, and l.  (If you don't get this - put your fingers on those keys; you'll see how useful that is.)  Typing '/' will start a text search of the current page (not very useful in Chrome since it's Find command, bound to Command-F on Macs, is bloody brilliant).  'H' and 'L' go back and forward in the History.  If you want to turn off the bindings, so that you can for instance type something into a web form, you hit 'i', and to turn the shortcuts back on, you hit ESC.  This might not sound sensible, but trust me that it makes eminent sense to anyone who know vim or vi.

You can also rebind commands to different keys, and add your own shortcuts too, so there's plenty of room for you to tweak any of the shortcuts you don't like, and to get creative with shortcuts that are particular to your own browsing habits.

I also found a third extension: Keyboard-Fu. This extension seems much more powerful, giving far more flexibility by letting you associate complex chunks of javascript to a keystroke.  Unfortunately, it's still in "alpha," which means it's likely incomplete and quite buggy.  It is, however, under vigorous development, so I remain hopeful.

Bottom line: keyboard shortcuts are all that.  If you're looking for a good way to use shortcuts in Chrome, then go with Vimium for now.  But keep an eye on Keyboard-Fu; it's got great potential.

Best. Wiki. Ever.

I've got a lot of good to say about foswiki, a recent and thriving wiki engine that evolved from another more established wiki.  There's lots of wiki engines out there, and I've tried a bunch.  But I keep coming back to foswiki because it strikes the best balance of all of 'em between flexibility, simplicity, and robustness.
Because the post wasn't really about foswiki as a productivity aid, I wrote it at my design blog.  If you're interested in wikis, you should check out foswiki.  As time goes on, I'll post here about how foswiki can be used as a productivity tool.

Appigo Todo is now in the comparison of task managers

I've been developing a comparison matrix of iPhone task managers as a Google Spreadsheet.  I've just finished adding an entry for Appigo Todo to it.  You can see the spreadsheet here.

My first original tool: formatting AutoFocus

Pulling together bits from a number of sources, I've come up with my first task management tool.  It's a slight enhancement to AutoFocus - not in terms of method but rather in format.  That is, one thing I've noticed about AF is that little is said about how to arrange things on the page; I've come up with one possibility in that regard.

Here's an image showing a page written up in my format.  The goal was to balance the utility gained by adding structure to the page against the extra work needed to add and maintain that structure.

I'm using a simple spiral bound, quad-ruled notebook here.  This image only includes sample notes and tasks because the real pages in my notebook all have private information.

I prefer quad-ruled paper because I can use the book in either portrait or landscape and still have a usable space.  And the grid of lines helps me when I doodle rather than write linear text.  (More on both landscape mode notes and doodling in a future post.)

First thing I do when I start a page is draw in a rather wide left margin.  The margin is used to basically "tag" entries with keywords and a few other things.  The margin can be thought of as for "meta data" about a task.

Next I put today's date at the top of the body of the page.

Entries come in two basic types: notes and tasks.

Notes are for things like meetings, and generally writing down ideas, rather than actions I need to take. Notes are distinguished by their general topic.  I put the topic in the margin, to mark the beginning of a new "chunk," then just write out the notes.  Sometimes a note might be just one or two lines long; other times it might be several pages long and have a variety of tasks embedded in it.

This is one particular advantage, I think, of this format: since notes and tasks are kept together, you can put pretty much anything at all into a single notebook.  Having everything in one place is a big deal for me; no more multiple booklets and scraps of paper in jacket pockets.

Blank lines are your friend here.  A simple spiral bound notebook can cost less than $2, so there's no reason to be stingy with space.  Vertical space is important to clearly mark boundaries between items and to make sure you leave space for annotations you may add to items in the future.  And if you're worried about the environment, then you shouldn't be using a paper notebook at all.  But that's another post too.

Tasks are marked by a small box in the margin.  The box is useful because it not only lets you separate tasks from notes very easily, but it's also an anchor for other bits of task meta-data.

Completed tasks get a checkmark in their boxes.  Cancelled tasks get an X.

Delegated tasks are marked with a left-pointing arrow through the box.  Optionally, you may want to put  a marginal note indicating the reason for delegation.  I don't, but it might help you.

Finally, if a task is hung waiting on something, then I put a small circle in the box - small enough to be plainly visible if the box is empty, and yet vanish pretty much completely if I put a check, or an X, or an arrow through the box later.

The very last task on the sample page shows a task marked as important (the exclamation mark at the left side of the margin), and having a due date (the date between the box and the exclamation mark), and a completion date ('way over on the right side of the page).  I like the idea of having the dates at either end of the task, representing a span of time as it were.  It also makes sure I don't confuse due dates with completion dates.

You can use any variation of AF with this format.  That is, the format lets you keep the information you write a little more organized just by the way it's put on a page, while AF in any of its forms helps you sort through the actual tasks and get them done.

I note that if you prefer other forms of paper notery for this format, you do have some choices.  Circa makes some very interesting notebooks - which I also use.  The beauty of the Circa notebooks is that you can rearrange the pages as in a binder, but also fold the cover back on itself as with a spiral-bound notebook.  You can buy pages for Circa that are either plain grid paper or pre-printed to have a large left margin, special locations for dates, and so on.  Or you can buy a Circa hole-punch and use whatever kind of paper you like.  Circa notebooks work well and look better than the goofy spiral-bound notebooks.  I like their touch of class.

There are other manufacturers of disk-bound notebooks like Circa (I mention a number of them here), but I haven't looked into the kinds of pre-printed pages they have and how that might impact the format I propose here.

So there you have it: a simple way to organize content on a page to help you use AutoFocus.  It works great for me; your mileage may vary.

---

If you're interested in how this format came about, here's the short version: I read an article by Mark Forster for lifehacker.com where he mentioned how nice it would be to have both notes and tasks in a single notebook.  At the same time I was playing around with orgmode, an editing plugin for the Emacs text editor that does just that: combining journaling and note-taking with appointment and task management.  These two things, plus the notebook I keep on my desk at home, just kind of merged one day. And out popped this format.  I've been using it ever since.  Indeed, I'm even thinking of hacking orgmode  to support my page format.

A fabulous fountain pen

I have a thing for pens.  Don't ask how or why, but I love pens.  And I especially love fountain pens.  Every Christmas, I allow myself a few pens to add to my collection.  This year, I added a few Chinese fountain pens to the list.  I did this because they look interesting, they're economical, and - in my experience - a good pen doesn't have to be expensive.

Boy, was I right.

A Wenliang 652

I've only tried one of the four pens that I bought: a Wenliang 652 stainless steel pen with a fine nib. It cost $3.90 USD and has free shipping - can't get much more economical than this!

The pen is a little heavier than typical pens (but lighter than, say, Rotrings), and very well balanced.  The cap fits snugly on the slightly recessed end (one of my greatest problems with fountain pens is when the caps don't stay on, and end up flying off - especially if I'm writing on the subway or a bus...).  It has a removable reservoir so that you can use cartridges if you prefer.  The reservoir I got looks different from the one in the images on eBay, but it still works fine.

What really got to me, though, was how smoothly it writes.  I can't recall the last time I used a fountain pen that just... floated across the paper like this $4 pen!  I charged it from a bottle of Sepia Omas ink I've had for at least a decade - I doubt that the ink made any particular difference.  Indeed, I should think ink that old might even do more harm than good.  And yet, the pen writes like a dream.

There's nothing like a good pen to help me a deliberate and attentive writer.  Seeing a fine, steady line of ink appear on the page, unskipped and unsplotched, somehow makes me think the words I'm writing are that much more important.  A good pen helps me write by giving me pleasure in the writing.

If you like fountain pens, you really should give this one a try.  (I'll let you know how the other Chinese fountain pens work out, when I get to them.)

In case you want to get a Wenliang 652 yourself, there's still 9 available on ebay as of this writing.